Aaron McCausland
05/07/2025, 10:37 PMCeligo AI
05/07/2025, 10:37 PMAI generated answer (using internal Slack threads):Based on the conversations, it seems like the unexpected error you're encountering when creating an Estimate for a specific Role could be due to a few reasons: 1. Role Permissions: Check the individual role permissions in the user's account > access tab. There might be some permissions that are not granted to this specific role which are causing the error. 2. Script Issue: The error could be due to a script that is being triggered when creating an Estimate. This script might have a restricted audience or might be deployed only for certain roles. You can determine the script deployment id from the URL address and check the audience on that script deployment. 3. Date Format: If your script is using date or time functions, make sure the date format in the script matches the user's date format preference. A mismatch in date format could cause an unexpected error. 4. Null Values: If your script is trying to access a field that is null due to permissions (directly or indirectly), then the role could be at fault. For example, if you have
foo.setHours
, it's foo
that is to blame, not setHours
. If foo
is left null due to permissions, then the role could be at fault.
Remember to debug the issue by replicating the role and permissions of the user experiencing the issue. This will help you identify if the problem is with the role permissions or the script.
******
Disclaimer:
This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes.
******Celigo AI
05/07/2025, 10:37 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.823313832
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.81117779
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.809469581
Celigo AI
05/07/2025, 10:37 PM