It looks like the issue is caused by how the backslash (\) is being handled in the query. Even though you are escaping it, Snowflake might still interpret it incorrectly.
A couple of things you can try:
1. Double escaping the backslash:
SHOW GRANTS TO USER \\\"ad\\\\snowflakeAnalytics\\\"
Some systems require \\ to be passed as \\\\ in JSON strings or API calls.
2. Using single quotes instead of double quotes:
SHOW GRANTS TO USER 'ad\\snowflakeAnalytics'
Snowflake sometimes handles escape sequences differently in single-quoted vs. double-quoted strings.
3. Verifying how the query is being constructed:
If this query is being built dynamically, ensure that the backslash isn’t being stripped or misinterpreted before being sent to Snowflake.
Could you test these and let me know if any of them work?
Just checking in to see if my response helped you.
If this solution resolved your issue, could you mark it as the accepted answer in the forum? This would help others facing similar challenges and also allow me to continue progressing on my journey as a SailPoint Ambassador.
Hi the double / was ready added , but the issue was with name attribute format in the snowflake system it is not standard in snowflake to have name with / so we were able to get snowflkae team update the account and then aggregation was successful.
I think a feature to filter accounts based on name in the connector would be helpful which can be called before the snowflake sql query is built