a custom transaction line field is sourcing it's value from the item. with the standard way of sourcing on the field settings. It works in the UI always, but orders from the web store (suitecommerce advanced) can sometimes skip to source it, not always though. What can be the cause?

AI generated answer (using internal Slack threads):

****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** The issue you're experiencing with the custom transaction line field not always sourcing its value from the item in SuiteCommerce Advanced orders could be due to a few reasons: 1. Sourcing Timing: The timing of when the sourcing happens could be a factor. If the item is not yet fully loaded or if some other process is interfering with the sourcing when the order is created, it could cause the sourcing to be skipped. 2. Script/Workflow Interference: If there are any scripts or workflows running on the order creation process, they could potentially interfere with the sourcing. This could be especially true if they are manipulating the item or the custom field in some way. 3. Data Inconsistencies: If there are any inconsistencies in the data between the UI and the web store, it could cause the sourcing to fail. For example, if the item is set up differently in the web store compared to the UI, or if the custom field is not properly set up in the web store. 4. SuiteCommerce Advanced Configuration: There could be some configuration in SuiteCommerce Advanced that is causing the issue. It might be worth checking the settings and configurations related to order creation and item sourcing. To troubleshoot this issue, you could start by checking the scripts and workflows that run during order creation, and see if they could be causing the issue. You could also check the data and configurations in both the UI and the web store to ensure they are consistent and correctly set up.