A recent issue/bug my agency is encountering for the past month (since the last patch) is we keep getting ERROR 000732 when we do anything involving an Add Join in a model. This issue was occurring inconsistently before, but is now more frequent if we make a new .aprx or utilize an older one. The reason we use model builder instead of manually Add Joining the tables is we have numerous datatables (csv, etc) that periodically update public facing dashboards, and we want this process automated. Before the last patch, we were not having this issue.
Our normal process in our Model build is Export Features > Add Join ( Input table to polygon layer) > Export Features.
The Add Join process validates successfully and the model runs as expected once. However, when we close out of the .aprx and reopen to Validate the model again, or use the def Statement in the Python window for a script, we keep getting ERROR 000732. It's as if the Add Join keeps losing connection to the polygon layer (despite how the layer is imported it into the .aprx's geodatabase). From Python:
'arcgisscripting.ExecuteError: Failed to execute. Parameters are not valid.
ERROR 000732: Layer Name or Table View: Dataset ADH_Counties_Layer does not exist or is not supported
Failed to execute (AddJoin).'
Now, if we use an older .aprx (pre version 3.0 of Pro) that utilizes the now deprecated Table to Table and Feature Class to Feature Class tools that essentially do the same functions, we don't get this error at all. My team and I tested this with a newly created .aprx stored on a network drive, and one on a local machine. We get the same results regardless. We did contact ESRI tech support to watch us repeat this process, and we're still awaiting an answer from them.
I've checked the fields on both the csv and the polygon layer, both are the same format. I'm looking for any suggestions as this issue is halting our regular weekly updates, and manually doing this is not an optimal solution.
