ArcGIS Pro 3.3.5 Edit with a temp join failing - Bug?

[BryanMc]

We have a point layer in SDE/SQL Server, archiving enabled, not versioned. We enabled "start/stop" edit mode in Pro 3.3.5.

We can edit the FC directly without issue. But when we join the FC to a table in a fileGDB by ObjectID, the join works fine, but we can't edit the source FC. One of two scenarios will happen: Start the edit session but the layer isn't editable; or Try to start editing but get an error saying we can't edit the FC since not versioned.

We flip to ArcMap, and it works as expected, we can edit attributes without issue. Not a great workaround as we are hoping to remove it soon. Anyone else encounter this or have a tip around it from Pro?

[Robert_LeClair]

I tested your described workflow using a PostgreSQL eGDB, archiving enabled on the FC, not versioned.  I configured ArcGIS Pro to have have "start/stop" edit mode in ArcGIS Pro 3.5.0.  I can edit the FC without issue.  I create a JOIN with the table coming from the project fGDB.  Then start an edit session and can edit the FC without any problems.  No error message.

So I wonder if it's an ArcGIS Pro 3.3.5 issue perhaps?  I don't see any reported bugs in the internals.

[BryanMc]

Hi @Robert_LeClair , thank you for taking the time to review. I did a few updated tests and it still doesn't work (3.3.2 and 3.3.5), sadly I can't test in 3.5.0 at the moment.

I made a copy of the FC into the fileGDB and it worked. I tried the join with keep-all and just matching and also made a copy of FC without archiving and no attachments in SQL Server - which the error still occurs. This is a 10.8.1 eGDB in SQL Server. So could be related to Pro version, or combo with eGDB version/db.

I will see if I can get a 3.5.0 Pro setup to test as well and hopefully have some success. I'll keep this open for the time being, but good to know it doesn't happen in all scenarios.

[JMutunga · Accepted solution]

@BryanMc what option do you have checked in the Options page for 'Enable and disable editing from the Edit tab'? 

For your workflow, I would expect the issue you are reporting if you have 'Single workspace edit session' checked since your feature class and table are in different workspaces. 

[BryanMc]

Thank you @JMutunga ,

It was set to Single Workspace. I switched it and it confirm it works. Although no thanks to the error message.

ArcMap was single WS and it still worked since you could only edit the parent in the join - but as now confirmed, Pro doesn't work in the same way. Agree that the messaging leads one to think there is something else wrong and not related to the WS config (see error image).

Still a bug IMHO, but on the messaging side of things and already a logged issue. Although hard to know if related since there are no bug details.

@DenisLalonde , appreciated your reply as well, and for sharing the related bug report! Next time we cross paths in Ontario, I owe you a pint!  Josphat, you can join too if up you come up north!

[DenisLalonde]

I was just having the same issue. 'Single workspace edit session' was the problem. Changing to 'Multiple WES' did the trick, but in an non-versioned EntDB environment, quite risky as edits are immediately committed without the chance of reverting. 😬

Related to this, there is an existing defect report to improve the messaging (thanks Esri.ca support for letting me know): BUG-000166229: In ArcGIS Pro, the Choose Workspace dialog box is not user-friendly.

Cheers,

Denis

[JMutunga]

@BryanMc I might take you up on your offer! Thanks about your feedback about the error messaging. That can be addressed separately from the bug @DenisLalonde mentioned. 

@DenisLalonde Single workspace edit session was mainly introduced to support discarding edits in a non-versioned workspace to avert the risk you mention. For your case, I hope changing to multiple edit session does not interrupt your workflow too much.