While creating time based charge rule in NetSuite, it does not accept 0 as rate multiplier from api but it does from ui. How can i pass 0 from api? The error was outside minimum range

AI generated answer (using internal Slack threads):

Based on the conversations provided, it seems that the issue of not being able to pass 0 as a rate multiplier from the API, while it is possible from the UI, is not directly addressed. However, there are some related discussions that might provide some insights. In the first thread, a user is trying to insert discount items with a negative percentage rate into a Sales Order via SuiteScript 2.0. However, the rate is added as a positive percentage. When trying to set the price level to Custom and set the rate as a negative percentage, they receive an error. A suggestion was made to set the rate field as a number without the "%" symbol. Another user suggested using

record.setText({ fieldId: "discountrate", text: "-10.0%" });

to set the discount rate, but noted that this might not work if the user has their negative number preference set to

(100)

. In the second thread, a user is trying to handle percentage changes outside the 0-100 range in a Suitelet. The suggestion was made to use a float field instead of a percent field, as the issue might be due to the percent field being bounded by a range of 0-100. In the third thread, a user is encountering a 'ROUNDING-ERROR' when trying to save a new sales order with a 0% tax rate and a sales discount item with a different tax rate using a map reduce script. This error only occurs for orders in the UK and does not occur when the order is created manually in NetSuite. While these discussions do not directly answer your question, they suggest that there might be some limitations or specific requirements when dealing with rates and percentages in NetSuite via SuiteScript or the API. It might be necessary to handle these values as numbers or strings, or to consider the user's number preferences. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******