Skip to main content
Solved

Using generated session variables for generating guid

  • September 15, 2023
  • 1 reply
  • 88 views

Gabriela Andes
Rookie
Forum|alt.badge.img

We are trying to use the generated session variable: select SESSION_CONTEXT(N'guid') in Universal GUI

I’ve added it in a sample task that will show the generated guid but the returned value are only 1s and 0s for all users. Do I need to configure something in SF or IAM in order to display a different GUID for each tsf_user()?

 

Best answer by Vincent Doppenberg

Hello Gabriella,

All of your guid session variables are the same because you are testing against an SF metasource instead of an IAM metasource. Indicium sets the guid session variable with the value of the use log session, as can be read here. For SF metasources, the use log session is always 1, because the SF does not track user sessions. So the resulting guid will always be 00000001-0000-0000-0000-000000000000 as well. You will get different guids per user and per user session if you test against IAM.

The guids for IAM metasources will always be xxxxxxxx-0000-0000-0000-000000000000, where xxxxxxxx is the hexadecimal representation of the use_log_session_id of that session.

select *
from use_log_session

So these guids are both predictable and easily derivable from data that is persistently stored in IAM, and therefore not suitable for the purpose mentioned in your previous topic.

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

1 reply

Forum|alt.badge.img+4

Hello Gabriella,

All of your guid session variables are the same because you are testing against an SF metasource instead of an IAM metasource. Indicium sets the guid session variable with the value of the use log session, as can be read here. For SF metasources, the use log session is always 1, because the SF does not track user sessions. So the resulting guid will always be 00000001-0000-0000-0000-000000000000 as well. You will get different guids per user and per user session if you test against IAM.

The guids for IAM metasources will always be xxxxxxxx-0000-0000-0000-000000000000, where xxxxxxxx is the hexadecimal representation of the use_log_session_id of that session.

select *
from use_log_session

So these guids are both predictable and easily derivable from data that is persistently stored in IAM, and therefore not suitable for the purpose mentioned in your previous topic.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings