Getting error while editing experience in AES - unable to fetch variable values for producer

prakashknow
Tera Contributor

‎11-11-2023 02:11 AM

Dear All,

 

Supposedly a weird behavior. I am a learner. I created an App, very basic app, with few fields, using AES, just to get some hands-on. Created a Standard catalog item (other experiences also created, but no issues yet). I tested it and worked fine. Issue is with Standard catalog item only, explained hereon. Later, I tried to add container with two columns and rearrange by moving the fields by drag and drop in the new format. All this from within the AES to organize it a bit. Objective was to stick to AES for all that is possible, without going to the "Maintain Items".  while saving, it said "unable to update the record", some kind of critical alert. I aborted and again when to edit the Experience to attempt one more time. This time while clicking to edit it says-> "unable to fetch variable values for producer".  Screenshots attached. Not sure what has gone wrong. 

 

Any pointer to resolve will help. Attached are screenshots.

Preview file
155 KB
Preview file
45 KB
  • 1,633 Views
6 REPLIES 6

Community Alums
Not applicable

‎11-21-2023 11:33 PM - edited ‎11-21-2023 11:46 PM

Hi @prakashknow 

 

It seems that you are getting error because either the right application scope is not selected, or the update is locked by another user update set and changes are not committed yet.

For Eg.   

 

If you will navigate to studio by being in the same scope you will get the details once you open your item that says something like below

 

"This record has been recently modified in update set 'Dummy1' by 'Dummy1' but not committed to the source control (View differences). To edit the record use update set 'Dummy1'

 

If the catalog is locked by 'Dummy1', please select update set as 'Dummy1'and edit or submit it will work. In other case if edit is locked by 'Dummy2' please select the current user update set and edit the record.

 

Workaround is simple if item is locked by anyone who is working then that change should be committed to make anyone else edit that item.

 

Hope it helps you!

Community Alums
Not applicable

‎11-23-2023 01:38 AM

Hi @prakashknow 

 

This issue made me do further investigation and fortunately able pinpoint the root cause that's main culprit here.

 

In nutshell, check this system property and disable it avoid this error: glide.ui.vcs.collision_avoidance 

 

So basically, this is happening due to 'Collison Avoidance.' It avoids modifying an application file across different update sets to ensure seamless experience during the commit process.

 

When the logged in user opens an application file that was modified in an update set different from the user’s current update set for the corresponding application:

 

  • Collision is detected in the application file and a warning message is displayed.
  • Logged in user to prompted to choose an update set.
  • Read-only protection policy is applied to the application file.

AbhishekPande1_0-1700732070286.png

 
User can make changes to the application file only after selecting the required update set.
 
Note: This feature is applicable to only those applications that are linked to GIT.
 

Enable or disable the collision avoidance feature using the glide.ui.vcs.collision_avoidance property in the System Property [sys_properties] table. By default, the feature is enabled. See Available system properties for more information.

 

You can check the SN reference doc link here: Collision Avoidance 

 

Mark this as correct response and helpful if it addresses this issue.

 

Thanks!