Hi, @take_vf.

Thanks for posting and for your patience. This is currently a bug [FMEENGINE-79011]. We apologies for any inconvenience this may have caused. We’ll keep you posted.

Thanks,

@AliAtSafe thanks for your reply. I could not find the bug listed among know issues for FME 2023. Are you working on a solution, and how long can I expect to wait? I have dozens of workspaces that use the Portal Feature writer that are the result of many hundreds of hours of work and now are unusable. Do you have a suggestion for what I should do in the meantime? Will rolling back to FME Server 2022 solve the issue?

Hi, @take_vf.

Thanks for your patience. Currently this bug is resolved for the purpose of making logging more readable when an error is raised in 2023.2+. The underlying error causing it to be raised (i.e., a user doesn’t have admin access to the feature service they are writing to and the capabilities declared on the feature service don’t match the feature operation they’re using) likely still exists. It might be easily fixable in other versions, if needed, by overwriting file(s). Let me know if this helps or needs more explanation, happy to help!

@AliAtSafe 

The account we use for writing from FME to our Enterprise portal has access to the contents of the entire portal, so this should not be an issue. But if you know of specific permissions that are needed in Enterprise I can double-check that the account has been granted these.

I would be interested in any potential solution to this issue, which files would need overwriting?

Hi, @take_vf.

We appreciate your patience.

We think the best recommended course of action is to try a build that has the fix from FMEENGINE-79011] (i.e., 2023.2+) to see if the issue is resolved. If it is not, then we’d like to kindly request to turn on debug logging to capture the HTTP traffic to see if we can diagnose / reproduce the error on our end.

Thanks!