Duration - Ideas how to CREATE or ENTER from BO1 to BO2

ninap

hi,

not sure why or how but this is unable to work;

CREATE BO2 WITH BO2.duration=BO1.duration

issue - cannot take the duration Data between 2 objects - both are exact same Attribute Type = DURATION, HH:MM, Calculated

any idea?

txs, nina p 😉

BobK

That should work. I have multiple similar rules. Although I do not use DURATION I would not think that would make a difference.

The only way that I can think of for that not to work is if BO1 is not in CONTEXT.

Have you checked the logs for clues?

ninap

hi,

yes it should be as we tested with

FIND BO1 WHERE THIS or THAT TAKE BEST 1

and even

FIND "query" TAKE BEST 1

I think it is a bug with DURATION fields as we tested now over 4 hrs with variations and all failed when the DURATION attributes are begin used.

txs, nina 😉

BenHayat

ninap wrote
hi,

yes it should be as we tested with

FIND BO1 WHERE THIS or THAT TAKE BEST 1

and even

FIND "query" TAKE BEST 1

I think it is a bug with DURATION fields as we tested now over 4 hrs with variations and all failed when the DURATION attributes are begin used.

txs, nina 😉

Nina, does it work with another Attribute a none-duration type? If yes, then BO1 is in Contex as Bob mentioned and it's an issue with Duration type. If no, then do a Display message before CREATE to display an attribute of BO to make sure it's in the context.

ninap

hi,

yes if we remove the attribute which is of type DURATION it all goes into the Object as planned.

so its a bug with DURATION then.

thanks for everyone pitching in!

nina 🙂

BenHayat

Nina, I suggest you create a small app to show the bug and send it to Support.

BenHayat

Nina, I just checked in my app, since we use Duration and we transfer it from one object to another, during create along with other attributes and it works fine.

ninap

exactly what I was doing... great minds think alike..

BenHayat

BenHayat wrote
Nina, I just checked in my app, since we use Duration and we transfer it from one object to another, during create along with other attributes and it works fine.

CLARIFICATION: Sorry, my mistake. The transfer of attributes are not done in the CREATE time, but rather on an existing objects (as an update).

ninap

maybe spoke to soon.. just worked in a small test app - very odd

BenHayat

ninap wrote
maybe spoke to soon.. just worked in a small test app - very odd

The good thing is that, it's not a bug and it's something under your control.

crisg0112

I don't know if its good practice or not BUT everytime I am creating an instance of a BO with initialisation, I use the NO VALIDATION NO RULES flag and so far, it is working for me.

ninap

very odd;

so here is based your everyones input we tested ni the real BSV;

1) FIND BO1 WHERE BO1.status='good' TAKE BEST

Does not add to context

2) FIND 'Using a query' TAKE BEST 1

Does not add to context

3) If on the process we have the BO1 Object as a Process Input - It works

Qn< But why do 99% of all other same Processes work - find something, its in context, copy or move it?

nina;:

BenHayat

Nina, if you already have Bo1 in context before running this process, it's best to passed the BO1 to this process rather doing a Find. This way is much cleaner.

ninap

Hi,

This is a scheduled process which runs every week.

It was meant to FIND data in BO1 then CREATE BO2 - super simple

We have about 32 other similar processes with do exact same

The only difference between those and this one is BO1 has 2 Duration fields which we are trying get. AND BO1 has many object Rules on Edit/IF NEW etc... BO2 has No Object Rules.

So this is why it makes no sense -