Hi, Anyone knows how could this make sense? We have a Client Script that is supposed to fetch a value from the applied-to bill and set it on the payment record, but all the lines have the

apply

value equal to

false

, how could this be?

Which entry point? field change or some other? And was the record already committed or is this a new uncommitted record?

pageInit - uncommitted record

When you open the record it's already got that apply value ticked right?

Yes

Hmm might be too early in the process to pick up in pageInit. I'd try looking at another entry point maybe post sourcing?

hmm, makes sense, will try it

If you console.log the id of the context.fieldId on post sourcing and the value of the "T" line this might give you a clues as to at which point you can rely on the values in the post sourcing process.

didn't work with postSourcing or with sublistChanged we disabled the field and used a user event script to do it

Almost always better to use a server side script over client imho.