why is it that when I try to change the pricelevel...
# ask-stanley-ai
m
why is it that when I try to change the pricelevel on an item on a sales order in suitescript, the pricelevel options disappear.
c
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, where the price level options disappear when you try to change the price level on an item on a sales order in SuiteScript, could be due to several reasons: 1. Base Price Not Set: If there is no base price set on the item, the price level options may not appear. 2. Customer Record Price Level: The price level is usually set by the customer and then by the sales/pricing tab on the item record. If there is no price level set on the Financial tab of the Customer Record, this could cause the issue. 3. Custom Price Set: If there's a custom price set for the item in the subtabs on the Financial tab of the Customer Record, this could override the price level options. 4. Workflow or Script Conflicts: If there are workflows or scripts running that interfere with the price level setting, this could cause the options to disappear. For example, if a script is setting the item field, it could be sourcing in the price level field, which will overwrite the changes you make. 5. Subsidiary Conflicts: If there are conflicts between subsidiaries, this could also cause the issue. In the context of a client script, you might be seeing the field change to the desired price level and then change back to the original due to the sourcing of the item field. To avoid this, you could use the
postSourcing
function instead. Also, if you're trying to prevent a specific price level for a specific currency from being updated on an item record, you might find it challenging due to the complexity of the Pricing Sublist / Pricing Matrix. It might be possible to treat it as a sublist, but the IDs involved could look unusual. Remember to thoroughly investigate all these potential causes to identify the root cause of your issue.
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.866921961
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.860175133
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.850362837
Please provide your feedback on this answer.