SessionVars not working as should

BLOMASKY

There seems to be a problem when updating the new in memory session vars.

Stuff that works fine using LoggedInSystemUser (LISU) do not work when using the session vars. It almost seems like there is a transaction that is started and not letting me have access to the data.

Example, I have a Parent / child grid on a VP.
In the parent when I click on a row, I have a process that saves the ID in a session Var. Then I have the child grid refresh with the query "FIND Child where Child.ob_parent = SessionVars.parentID. This does not work but changing the sessionVars to LISU it works fine.

Bruce

aware_support

This seems to work fine for us. Would you be able to create a small BSV that demonstrates the problem?

aware_support

Definitely works for us. Please send the BSV

PointsWell

Bruce,

Did this ever get fixed? I am having the same problem.

I am assuming it is a typo your example code seems to have an error

FIND Child where Child.ob_parent = SessionVars.parentID.

It seems that an object is being matched with an ID

customaware

Wouldn't it need to be....?

FIND Child where Child.ob_parent.ID = SessionVars.parentID

BLOMASKY

ParentID WAS pointing to a BO. (sorry, bad naming).

Bruce

nhofkes

I have found earlier that the in memory session object (which by definition is not persisted) cannot be used for multiple reference attributes (1-n). It seems that the additional cross reference tables that are used for those attributes are not stored in the session object, therefore the reference attributes are not resolved. The work around is either to store the ID itself in the session object (rather than using multiple reference attributes), or use a persisted object for this purpose.
See also this earlier thread.

However, single reference attributes are possible I think.