You are viewing limited content. For full access, please sign in.

Question

Question

Variable name change on import

asked on April 23, 2021

We recently had an interesting issue occur and I wanted to see if anyone else has experienced this or might know of a way to stop it from occurring. We have a forms process with a variable "Requester_Email" however upon importing this process into Production this variable somehow became "Requester_Email_1" and processes got suspended because sending an email to "Requester_Email" failed. We checked both Staging and Instances from before the Import and there was no "Requester_Email_1" in Staging or on instances from before the import.

To get it working we added "Requested_Email_1" to the Send To on the Email Tasks and then exported the process so we could move it back into our Staging Environment. 

Upon importing the Forms Process into Staging, we got a new variable "Requester_Email_1_1". The variable "Requester_Email_1" was still there, however more troubling is it seems "Requester_Email" was no longer a variable... 

 

Note the missing email icon on the /Requester_Email entry. Validating the Imported Process gave "The name 'Email Requester' should not be shared by activity or events." and listed the email tasks with it. 

I tried finding if anyone else had encountered this issue but a search which included "_1" was returning anything with a 1 in it.

Using Forms Version 10.4.5

0 0

Replies

replied on April 26, 2021

Can you open a support case through your SP so we can take a look? In short, we believe there is a mismatch between your variable names and variable IDs that we could fix with the process XMLs and running a script to clean up the database.

If you want a somewhat confusing guess as to what happened:

My guess is, while you had your process in both the staging and production environments, the variable Requester_Email was deleted and recreated with the same name in production. When you next imported from staging to production, the staging process had Requester_Email with a different variable ID so it was automatically renamed Requester_Email_1 on import. Now, you would have both Requester_Email and Requester_Email_1 in your production process, yet your staging process was still unchanged. 

Then you imported that production process back into staging with both variables, where Requester_Email_1 in production had the same variable ID as Requester_Email in staging. So that update renamed Requester_Email to Requester_Email_1, then tried to add Requester_Email_1, saw it already existed and instead created Requester_Email_1_1. 

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.