API / SMU954 Issue

I have a custom procedure that creates an xml out to the web and an xml is sent back from the web which is processed through the API. The problem is the xml response comes back with a record id to keep things synced up and tries to write to the Contact F/M and the user is still on the record. I know that the API functions the same as if a user is setting at a keyboard entering the data and two people can not edit the same record. This causes a problem with the listener which renames the xml with a .x but it does a hard stop on the listener. (kills SMU954) Has anyone else run across this issue and come up with a fix?

Find more posts tagged with

Comments

Legacy Contributor

are you able to turn off soft locking on the F/M?

Legacy Contributor

TU 16782 which will be out in the 7.7.5 incremental may take care of this for you.

SMF999
12005 if use_soft_locking$<>"Y" or (%_run_bg and %_publish_only) then ok=1; goto *return

joe

Tim@ This current issue is with a customer on 7.6 and I do not see the soft lock flag. Is there anyway to stop SMU954/SMU955 from doing a hard stop for record locks and pop message type errors? Can you not just leave the .x in place and go on to the next file?

Stephanie@ I'm not sure that (%_run_bg and %_publish_only) will take care of the issue either. FM updates through the API are not going to be a %_publish_only process is it? ? ?

I looked at the code in SMC270, but did not see any logic that would allow the update. I don't think the user term_id and user_code are going to match up with the API process.

Copyright © 2025 Infor. All rights reserved.