Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAV 2018 SourceTableTemporary not working correctly?
Lilithyan
Member Posts: 32
Hello everyone,
either my memory is faulty or the Page-Property SourceTableTemporary is different in NAV 2018 than before. I remember using it in earlier Version (e.g. NAV 2016) like this:
If you use the property for a page with the sourcetable customer for example, fill it with one record for a customer, changes done on the page should not be actually saved within the database unless I specify this via code.
If I do this in NAV 2018 no matter what I specify upon having closed the page. the changed have been written to the actual record in the database (no matter if there was programming in the OnValidate Trigger for the field or not).
Am I remebering Things completely wrong?
Thanks in advance for any answers!
Ciao,
Lils
either my memory is faulty or the Page-Property SourceTableTemporary is different in NAV 2018 than before. I remember using it in earlier Version (e.g. NAV 2016) like this:
If you use the property for a page with the sourcetable customer for example, fill it with one record for a customer, changes done on the page should not be actually saved within the database unless I specify this via code.
If I do this in NAV 2018 no matter what I specify upon having closed the page. the changed have been written to the actual record in the database (no matter if there was programming in the OnValidate Trigger for the field or not).
Am I remebering Things completely wrong?
Thanks in advance for any answers!
Ciao,
Lils
0