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

Question

Question

template field changing when a different field is clicked

asked on October 16, 2023

I have a folder template with seven fields. The first, fourth, and sixth fields are required, The first, second, and seventh fields are numeric. I created the folders in the repository from a text file using Workflow, assigning the metadata at that time, e.g.,

     1990921914|123456|A|Wayne|McCoy|Bush|2|
     1995018867|205930||Dennis|Andre|Manning|3|

On one folder, I saw where the second field had an incorrect value. I opened the metadata.

When I clicked on the second field to enter the correct value, the value in the first field changed to all 0's.

I entered the correct value (116299) in the second field.

When I clicked back in the first field, the correct value appeared in place of the 0's. However, the second field reverted to the incorrect value. 

When I click OK with the first field all 0's and the correct value in the second field, the values revert just before the screen disappears. If I reopen the metadata, the first field contains the correct value and the second file contains the incorrect one. If I click in the second field, the first field changes to all 0's and the correct value appears in the second field.

 

Any ideas on how to correct this will be greatly appreciated.

0 0

Answer

SELECTED ANSWER
replied on October 16, 2023

It's just on the edge of your screenshot, but it appears that there is a custom format set up for the PR Number field. If you reset that to default, does that solve the problem?

0 0

Replies

replied on October 16, 2023

What other configuration do these fields have? Any constraints or custom formatting? It seems like the actual stored value is correct, and there's something wrong with the way it's trying to display it to you.

0 0
replied on October 16, 2023

Here is the template definition. The only constraint is the PR Number must >=1000000000 & <=9999999999. The input status is a number that is converted to text by the workflow.

0 0
SELECTED ANSWER
replied on October 16, 2023

It's just on the edge of your screenshot, but it appears that there is a custom format set up for the PR Number field. If you reset that to default, does that solve the problem?

0 0
replied on October 16, 2023

That actually solved the problem. The custom format was 9999999999, just like the upper constraint. I put it in last year when I started work on this repository because the general format included a decimal point and it appeared to be working fine. I had to stop work on this repository in February to work on one for our Accounting-Payroll group. I restarted work on this one a couple of weeks ago. This is not the only thing I have found that works differently now from the way it did back then.

 

Thanks.

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

Sign in to reply to this post.