help with data clean up process

nlarson

I created a few processes which I would like to use to populate some new fields I have added to my BSV; but I just don't understand the results. I have tired so many variants I think I am going in circles. What I want to do is:

Find all instances of a BO, Then update an attribute in each instance with a value from a reference of that instance.

The closest variant seems to be:
FIND ALL Measurements ORDER BY Measurements.ID IN BATCHES OF 100
Measurements.Title=Measurements.MetricsReference.Metric

What this does is set all Measurements.Title to a single value (i assume the first one it finds) rather then their own value.

I have tried 'This', and 'That' as modifiers and I have also dropped this into a 2 part process, but that does not seem to find the right context.

Any ideas? I'm on hour 5 here and just started talking to myself 🙂
😃

tford

Might want to check here:

nlarson

Thanks Tom I had tried the 2 process approach, but had issues. I ended up doing this to solve it.

moved all rules into the BO
changed the process to UPDATE
learned that <>'yes' is not the same as IS UNDEFINED - when adding the new field all values were null so <>'yes' found no results.

rocketman

Curious.... The two process approach works every time for me.

Was the second process set up to use the measurements context? (yes I know that's a newbie type question but sometimes -especially after 5 hours, we get blurred vision)

Is MetricsReference a single ref not a multiple.

Would have thought that <> 'yes' should have worked since undefined would not be = to 'yes'

As I said - just curious

nlarson

rocketman wrote
Curious.... The two process approach works every time for me.

Was the second process set up to use the measurements context? (yes I know that's a newbie type question but sometimes -especially after 5 hours, we get blurred vision)

I did some clean up and deleted the version with the clean up rules so I can not check, but let's just say I can't say with certainty that you are wrong :oops: Bottom line, I got what I needed and it seems likely I could have gotten there much sooner If I had made some error along the way!

rocketman wrote
Is MetricsReference a single ref not a multiple.

Would have thought that <> 'yes' should have worked since undefined would not be = to 'yes'

As I said - just curious

This one still has me stumped. I use <>'yes' often, but when I ran the process with IS UNDEFINED got 96 results, with <>'yes' the logs show 0 found. It was an easy fix, just did a UPDATE SQL script and all was Good To Go.

jacklcs

FIND ALL Measurements ORDER BY Measurements.ID IN BATCHES OF 100
Measurements.Title=Measurements.MetricsReference.Metric

Try to change IN BATCHES OF 1

thanks,