I'm testing out dynamic table columns in collections based on user language.
F
Fathia Jama
started a topic
almost 2 years ago
I'm testing out dynamic table columns in collections based on user language. It seems that once loaded, the collection is cached and does not reassess the dynamic values in it. Is there a way to go around this behaviour?
Best Answer
F
Fathia Jama
said
almost 2 years ago
Hello Luc,
model variables are refreshed by default :
every 30 minutes
when the admin refreshes the app
when the model is deployed
I suppose that you are currently changing the user's language on the fly for testing purposes, right? Then you should refresh the app to take your live-changes into account. I suppose that your users will not change their preferred language once defined, so the current behavior should be good. But if not, don't hesitate to create your custom function that takes as an argument the :V_USERNAME variable (this one cannot be changed on the fly), and returns its language from MTA_USER->LANGUAGE. There no cache on the repository table.
I hope this helps.
Best regards,
Stéphanie.
1 Comment
F
Fathia Jama
said
almost 2 years ago
Answer
Hello Luc,
model variables are refreshed by default :
every 30 minutes
when the admin refreshes the app
when the model is deployed
I suppose that you are currently changing the user's language on the fly for testing purposes, right? Then you should refresh the app to take your live-changes into account. I suppose that your users will not change their preferred language once defined, so the current behavior should be good. But if not, don't hesitate to create your custom function that takes as an argument the :V_USERNAME variable (this one cannot be changed on the fly), and returns its language from MTA_USER->LANGUAGE. There no cache on the repository table.
Fathia Jama
I'm testing out dynamic table columns in collections based on user language. It seems that once loaded, the collection is cached and does not reassess the dynamic values in it. Is there a way to go around this behaviour?
Hello Luc,
model variables are refreshed by default :
I suppose that you are currently changing the user's language on the fly for testing purposes, right? Then you should refresh the app to take your live-changes into account. I suppose that your users will not change their preferred language once defined, so the current behavior should be good. But if not, don't hesitate to create your custom function that takes as an argument the :V_USERNAME variable (this one cannot be changed on the fly), and returns its language from MTA_USER->LANGUAGE. There no cache on the repository table.
I hope this helps.
Best regards,
Stéphanie.
Fathia Jama
Hello Luc,
model variables are refreshed by default :
I suppose that you are currently changing the user's language on the fly for testing purposes, right? Then you should refresh the app to take your live-changes into account. I suppose that your users will not change their preferred language once defined, so the current behavior should be good. But if not, don't hesitate to create your custom function that takes as an argument the :V_USERNAME variable (this one cannot be changed on the fly), and returns its language from MTA_USER->LANGUAGE. There no cache on the repository table.
I hope this helps.
Best regards,
Stéphanie.
-
Extend a model with new entities or attributes
-
Data types in xDM
-
Effective date on entities
-
Search using wild cards
-
Export a model from production and import on a development environment
-
"Allow Delete" vs "Allow Removal" privileges
-
LOV label in Named Query
-
Select location on a map and save coordinates
-
Is there a way to set up a master-detail relationship on browse mode?
-
Choose Either a Stepper or A Workflow Based on The User Privileges
See all 209 topics