Hi, maybe you can try this: the idea would be to have two data sources/base views, one for the 'login' and other one for the 'data' request:
- The first view will return the session_id as an output field.
- The second data source should be configured to have an HTTP header like 'Cookie=@sessionid'. This way the base view will have a mandatory input parameter (sessionid).
Finally, you will need a third view (a NESTED join view, using 'sessionid = session_id' as join condition) so when a user executes this view, it will fetch the session_id from the left side of the join and then, once done, it will get the data from the second view. And, if you know the valid time to live for the session_id, maybe you can cache its value to reuse it between executions.