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

Question

Question

{/dataset/_instance_id} Is Not Populating Field With Instance ID

Forms
Updated November 13, 2024
asked on July 13, 2017

I have duplicated this problem in Forms 10.2.1.205 and also 10.2.1.157. I have set a single line field to have the default value of {/dataset/_instance_id}. After the initial submission of the form, the field is not populated with the instance id, but is blank. Is this a bug? The {/dataset/_instance_id} is used to name the instance and it does populate the instance id for the instance name correctly.

2 0

Answer

SELECTED ANSWER
replied on May 30, 2019

The selected answer is probably not very clear on this. The instance ID does not exist until the form is submitted. After that point, it is available for use in subsequent steps. Forms does not go back to backfill the starting form if you used the instance ID variable in a field on that form.

So the behavior you're seeing is correct. In the starting form Tlog was empty because there was no instance ID at that time. In the next form, you're still not setting Tlog to anything, so you're seeing the "current" empty value.

1 0

Replies

replied on February 17, 2021

I have been trying to do the same thing and have had the same results, so I tried a different tactic.  I added the instance ID in the label of a field.  When I do that it shows on my form.  See screenshots enclosed.

LF Instance ID on Form.docx (18.3 KB)
Download
2 0
View 2 previous replies
replied on May 29, 2024

Thanks Roberta,

This worked for me. 

Christine

0 0
replied on November 13, 2024

Can anyone tell me why THIS works, on the second form in a process, but filling the field value does NOT work?  This is weird.  The first form has already been submitted, so the instance ID is there, but it won't populate on the second form in the instance?

0 0
replied on November 13, 2024

Katy, a Field Label is not saving the value. It is simply pulling whatever the current value is for the variable being used. As Miruna mentions above, the value of a field is saved when the form is submitted. Since the instance ID is not created until the initial submission of the form, there is no value to insert into a field variable and it ends up saving an empty value, which carries through the following steps because the "value" has already been set.

0 0
replied on November 13, 2024

So, maybe I can explain better.  I submit a starting form. In the task for the "approver" I want to have a field with the instance ID in it.  So on form 2 I have Instance ID field with the default value of {/dataset/_instance_id}.  But it doesn't show up in form 2.  It will show up in the label for form 2, but not the field.  It was working before our update to version 11 update 5 (yesterday). 

But today... 

0 0
replied on November 13, 2024

I got it!  The form was in read only mode!  Ugh!

0 0
replied on May 30, 2019

I have the same issue.  I have defined the default value as {/dataset/_instance_id} for variable TLog.

I submit the form.  Then I have a user task using a different form amd I add the variable Tlog to the form.  The instance id is not populated on the second form.

1 0
SELECTED ANSWER
replied on May 30, 2019

The selected answer is probably not very clear on this. The instance ID does not exist until the form is submitted. After that point, it is available for use in subsequent steps. Forms does not go back to backfill the starting form if you used the instance ID variable in a field on that form.

So the behavior you're seeing is correct. In the starting form Tlog was empty because there was no instance ID at that time. In the next form, you're still not setting Tlog to anything, so you're seeing the "current" empty value.

1 0
replied on May 30, 2019

Thank you

0 0
replied on July 13, 2017

That sounds like it's working as expected to me. The fields are saved as they were at submission time, Forms doesn't go back to backfill the value once the instance starts and an instance ID is assigned.

0 0
View 5 previous replies
replied on July 13, 2017

So I would need a secondary form that has the Instance ID field with the default value set in order for it to be populated and assign it to a user task?

0 0
replied on August 23, 2017

Hi 

I have the same problem here, but for me sometimes work sometimes don't.  Any suggestion Miruna?

Best regards

 

0 0
replied on January 3, 2018

Hello

I am facing same issue, so what would be the solution?

0 0
replied on January 3, 2018

You would want to make a copy of the initial form and add a field for the instance id and set the default value. Then assign the form to the following user task.

2 0
replied on May 15, 2018

When you say set the default value do you mean select the instance id token variable or actually input a set value?

0 0
replied on May 15, 2018 • Show version history

Yes facing the same problem.  I tried to do as you recommended and create a "single line" field and also tried it with the Number field and make "{/dataset/_instance_id} as the default value in both these fields in the initial form When the initial form is submitted, then I assign the the second form to the  reviewer and use these same fields to grab the value.  On the second form, I tried with the default value still in it and with out the default value in it and it still doesn't display.  I have version 10.3.1.553

1.PNG
2.PNG
1.PNG (3.95 KB)
Download
2.PNG (4.25 KB)
Download
0 0
replied on May 15, 2018

The instance ID will only be populated after the form has been submitted.

2 0
replied on August 14, 2019

The Instance ID is only Created once your first Form has been submitted as previously stated, I have tried to populate the Instance ID into a Field, however this wont work and the only way that i could set this up was referencing this in Custom HTML, or place it in the description, and use CSS to manipulate it.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...