I have a SAIL challenge, a form, in which I'm pulling live data from another

@richard.nolan Understood, so far I have gone through your code, I didn't find issues related to scope of variable. To reiterate, the values of the read-only components or the components which you may not interact with, should be saved under a component which you definitely make a interaction with.

Further it is also stated in the documentation that 'A user can only update a variable by interacting with a component that has the variable in the component's saveInto parameter.' (Reference: 'Enabling User Interaction' section at https://forum.appian.com/suite/help/7.9/SAIL_Design.html).

Copying the pieces of code which saves value into local!tir_project.project_manager_name and local!tir_project.project_name into 'saveInto' area of 'Next' button of Step 2: Project Details resolves the issue.

For instance, in order to save the value into local!tir_project.project_name irrespective of the interaction, you can do as follows:

a!buttonWidget(
label: "Next",
style: "PRIMARY",
value: 3,
saveInto: {
\ tlocal!currentStep,
\ ta!save(local!tir_project.project_name,if(rule!APN_isBlank(local!tir_project.project_name),index(local!resultSet.data,"projectname",null ),local!tir_project.project_name))
\ t},
validate: true
)

@richard.nolan Understood, so far I have gone through your code, I didn't find issues related to scope of variable. To reiterate, the values of the read-only components or the components which you may not interact with, should be saved under a component which you definitely make a interaction with.

Further it is also stated in the documentation that 'A user can only update a variable by interacting with a component that has the variable in the component's saveInto parameter.' (Reference: 'Enabling User Interaction' section at https://forum.appian.com/suite/help/7.9/SAIL_Design.html).

Copying the pieces of code which saves value into local!tir_project.project_manager_name and local!tir_project.project_name into 'saveInto' area of 'Next' button of Step 2: Project Details resolves the issue.

For instance, in order to save the value into local!tir_project.project_name irrespective of the interaction, you can do as follows:

a!buttonWidget(
label: "Next",
style: "PRIMARY",
value: 3,
saveInto: {
\ tlocal!currentStep,
\ ta!save(local!tir_project.project_name,if(rule!APN_isBlank(local!tir_project.project_name),index(local!resultSet.data,"projectname",null ),local!tir_project.project_name))
\ t},
validate: true
)