Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Fusion - Getting oldTextVal or oldState on 2 different fields

Avatar

Level 10

I have a scenario that looks for changed field value "Job Number" and then adds it to the beginning of the Project Name resulting in "ABC123456 Name Of Project". All good.

But if a user changes the job number later on, I end up with "XYZ456789 ABC123456 Name Of Project". It adds the new job number without deleting the old one.

I added a router and a filter "if oldTextVal=notExists" then concat the job Number & Name. And another path that says "if oldtextVal=Exists" then...

here I would like to undo the original concatenation by reverting the job name to the "old state" before concatenating the new job number with the original job name.

I can't figure out a way to get the old job name before the job number was added. I can't do "oldTextVal" without another field watch and it won't let me watch 2 fields in one scenario.

Any ideas?

0694X00000FQoPbQAL.png 0694X00000FQoR3QAL.png

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hi,

the old/new data is only in relation to the status of the fields right before the update that triggered the scenario, so since the "Original Project Name" w/o the prefix has been overwritten probably some time ago, you will not see that here. I would solve this issue by adding a custom field to the project "DE:Original Project Name" and set it in the route "OldTextVal=null" so you can get it whenever you need it.

If an updated job-number comes in, just get the value from "DE:Original Project Name" and use that for your Concat function.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 6

Hi,

the old/new data is only in relation to the status of the fields right before the update that triggered the scenario, so since the "Original Project Name" w/o the prefix has been overwritten probably some time ago, you will not see that here. I would solve this issue by adding a custom field to the project "DE:Original Project Name" and set it in the route "OldTextVal=null" so you can get it whenever you need it.

If an updated job-number comes in, just get the value from "DE:Original Project Name" and use that for your Concat function.

Avatar

Level 2

We actually have a similar process to what Chris described. We have a custom "Project Title" field that we set as a required field, and have trained our users to use that instead of project name. We then have Fusion creating a job number, and concatenating the job number and project title fields together.

The nice thing about doing it this way is that if someone accidentally edits the project name, Fusion will go back and rename the project to match the job number and project title fields.