I know we cant trigger UE by UE (after submit) but...
# suitescript
d
I know we cant trigger UE by UE (after submit) but there is a good way to achive that ? for example using UE that calls a scheduled/suitelet that execute the load/save for a record to trigger another UE ?
a
....yes? I'm not sure what you're looking for? you've answered your own question
d
I have a UE script (not mine) that's need to be trigger on creation of transaction. the issue is that's the transaction is created by SOAP and the UE cant handle it (for some reason..)
a
is the deployment limited by execution context? or is there some conditional at the start of the script makes it only process in certain execution contexts?
I'm not aware of any specific issues around SOAPs just ignoring UEs, that would be horrible.
d
the owner of the script cant make it work for SOAP so I need to handle it in another way
a
ok well I'm not sure why that would be the case, but just ignoring that, you can have the UE trigger a MR or SS and pass its type and id in as parameters, and then just have the MR or SS just do a load/save. similarly, you could just call a suitelet from the existing UE to do the same thing. like I said you answered your own question, all the options you suggested are workable.
d
Ok I just needed another brain to think with me thanks
👍 1
a
if you're unconcerned with this being done right away you could also schedule an MR and have it search for records which haven't been updated appropriately (assuming you can create search filters for that) and just have it run every day / hour / every 4 hours or w/e works
m
Check what your preference for "Run SuiteScript and Workflow Triggers" is (either company wide or on request level) https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_4170181850.html#bridgehead_4629750371
c
a workflow action script can trigger a UE if you have to have it.
116 Views