Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Greg Enns]

I want to execute specific code anytime Field1 is modified on a record we’ll call Rec.

So I created an event subscriber to the OnBeforeModify event with a simple if statement:
IF  xRec.Field1 <> Rec.Field1 THEN …

I created a test codeunit that did this:
Rec.GET;
IF Rec.Field1 = 0 THEN BEGIN
      Rec.Field1 := 5;
      Rec.MODIFY;
END;
Using the debugger, I stepped through line by line, and the first code to execute after the MODIFY is my subscriber. Once in the subscriber function, the debugger shows that xRec.Field1 and Rec.Field1 are both 5. 

What would cause this?

——————————
Greg Enns
ERP Coordinator
Technical Prospects
Kaukauna WI
——————————

[Naveen Jain]

You code should trigger on the OnValidate of the field.

——————————
Naveen Jain
Director of IT
Symbex Companies
Santa Fe Springs CA
——————————
——————————————-

[Greg Enns]

Hi Naveen,

That trigger is skipped if the field is set in code like in my example above. That’s why I chose not to use that trigger.
This blog? shows how OnBeforeModify event is supposed to hold the xRec values.

——————————
Greg Enns
ERP Coordinator
Technical Prospects
Kaukauna WI
——————————
——————————————-

[Suresh Kulla]

Greg,
I just tried a simple example with showing the rec and xrec values with message box and they are showing different. One thing I noticed is you are using Rec.GET which will again retrieve the old record and that could be the reason why both values are the same, why are you using Rec.GET statement.

——————————
Thanks
Suresh Kulla
NAV Technical Architect
ArcherPoint Inc.
Atlanta GA
——————————
——————————————-

[Greg Enns]

Thanks . Sorry I was unclear.
My Rec.GET? was just for my test code to modify the record.
So the full code looks like this…
Test Codeunit  OnRun
Rec.GET(‘PK1’);
IF Rec.Field1 = 0 THEN BEGIN
      Rec.Field1 := 5;
      Rec.MODIFY; (This triggers the event)
END;

Event Function OnBeforeModifyRec
IF xRec.Field1 <> Rec.Field1 THEN
     Executecode…

If I modify Field1 in the UI manually, then the Subscriber function recognizes the change and knows that xRec.Field1 <> Rec.Field1. But when I modify it via code like with my test codeunit above, then xRec.Field1 = Rec.Field1. I just tested this on a stock NAV table.field, and got the same results.
If I add an xRec.GET at the beginning of the Subscriber everything works properly. 
Is this a bug? Is it fixed in a later CU?  I’m on NAV 2016 CU 19.

——————————
Greg Enns
ERP Coordinator
Technical Prospects
Kaukauna WI
——————————
——————————————-

[Suresh Kulla]

Did you try using Rec.MODIFY(TRUE) instead of Rec.MODIFY.

——————————
Thanks
Suresh Kulla
NAV Technical Architect
ArcherPoint Inc.
Atlanta GA
——————————
——————————————-

[Greg Enns]

Yes. No luck. I also tried  Rec.VALIDATE(Field1,5);
That didn’t work either.

——————————
Greg Enns
ERP Coordinator
Technical Prospects
Kaukauna WI
——————————
——————————————-

[Jason Wilder]

Certainly seems to be a bug.  I get the same behavior in NAV 2017.  At least you have a work around which is to GET xrec.  I did something like this per your suggestion (using the Customer table in my example):
xRec.GET(xRec.”No.”); and everyting seems to work fine.

I think it would be a good idea for people to check their Subscriptions to see if they are using Xrec in an OnBefore Event and make this change at the top of the EventSubscriber Function if they are.

Good find!

——————————
Jason Wilder
Senior Application Developer
Stonewall Kitchen
York ME
——————————
——————————————-

[Greg Enns]

Thanks for testing this on 2017  ! 
Anybody able to help submit this to Microsoft?? I’d be happy to be part of the process–I’ve never done it myself.

——————————
Greg Enns
ERP Coordinator
Technical Prospects
Kaukauna WI
——————————
——————————————-