Suitelet set to Execute as Role: Current Role still runs as an administrator

AI generated answer (using internal Slack threads):

Based on the conversations, it appears that the Suitelet's "Execute as Role" setting determines the permissions level at which the Suitelet runs. If it's set to "Administrator", the Suitelet will have full access to perform any operations, including those that require administrative permissions. However, if it's set to "Current Role", the Suitelet will only have the permissions of the current user. In the first conversation, a user was able to resolve an issue by setting the "Execute as Role" to "Administrator" for a Suitelet deployment. This allowed them to submit a scheduled script via the Suitelet. In the second conversation, a user encountered a "Permission Violation" error when trying to perform a search.lookup operation in a Suitelet set to "Execute as Role - Administrator". The error was resolved when they changed the "Execute as Role" to "Full Access". It was also mentioned that client scripts run with the permissions of the current user, and to allow external users to use a Suitelet with an attached client script, the client script should make a request to a Suitelet to perform the search. In the third conversation, a user asked if it's possible to run part of a script as an administrator when the script is deployed as "Run as Current Role". The response was that it's not directly possible, but a workaround could be to have the code that needs to run as admin in a Suitelet set to run as admin, and call that Suitelet using HTTPS from the main 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. ******