- Jeff Wayt
- PowerServer
- Tuesday, 18 April 2023 02:31 PM UTC
I have a PFC application I migrated from 2017 R2 to 2022 and deployed as both Win32 target and Cloud target on my local machine. I began testing the proof of concept cloud app.
Windows retrieve fine, but when I try to add a record that uses PFC LINKAGE it gives me an duplicate key error. Doing the exact same thing in the Win32 app, it works fine. Debugging the cloud app, the app gave me "Transaction does not exist" as I stepped thru the pfc_save, even though it had to retrieve security, validate the user and menu access. Seems an artifact of debug, but it masks discovery of the issue.
I was able to add a simple, non-linkage row in a different PFC window successfully, so there is something about PFC Linkage that fails to translate. I can get duplicate key errors adding a single parent row & saving, or retrieving a parent and adding a child row.
Has anyone seen this? Is there something I need to do to the PFC, like using AFC? The literature says it supports PFC. The n_cst_dwsrv_linkage service was not modified.
Thanks in advance.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.