Scenario Context : I'm submitting a timebill paylo...
# ask-stanley-ai
s
Scenario Context : I'm submitting a timebill payload using SuiteTalk SOAP APIs with a custom timebill form. I’m encountering an “*INSUFFICIENT_PERMISSION*” error for the "Rate" field on the TimeBill form with SOAP submissions. 1. After enabling the "Rate" field at the form level and setting its Display Type to "Normal," submissions worked initially. 2. However, the field later auto-disabled without any changes made, and re-enabling it still didn’t resolve the issue. Is this a known bug, or has anyone else experienced similar behavior?
c
AI generated answer (using internal Slack threads):
Based on the conversations, it seems that the "INSUFFICIENT_PERMISSION" error you're encountering with the "Rate" field on the TimeBill form with SOAP submissions is not an isolated incident. Other users have reported similar issues with different fields when using SOAP APIs. One user mentioned that they were able to resolve their issue by understanding the process of creating the sales order in the UI first. In your case, it might be helpful to understand how the TimeBill form works in the UI and ensure that all necessary fields and permissions are correctly set. Another user suggested checking if the field can be changed using the UI. If it can be changed in the UI, then it should also be possible to change it using the SOAP API, provided that all necessary permissions are granted. In some cases, the error message indicates that the field is read-only, an associated feature is disabled, or the field is available either when a record is created or updated, but not in both cases. You might want to check these aspects for the "Rate" field. Remember to ensure that the user or role associated with the SOAP API call has the necessary permissions to access and modify the "Rate" field. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.813813925
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.813147545
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.80913645
Please provide your feedback on this answer.
s
Can you elaborate on the last point "In some cases, the error message......"