Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
A safe way to use temporary records
samantha73
Member Posts: 96
Hi Guys
I have tried a couple of variations of the temporary record to display results on a page and report. First below example
The problem is with table trigger = true , it deletes related records. I have seen recommendations to use above without true such as deleteall() but the problem is by mistake someone else can modify this code to True or I can leave True and actually delete records on the source actual table.
So I prefer creating a brand new table of with:
TableType = Temporary;
Now I have to populate this table and display on a page at run time and if required I can union other tables. Same can be done on RDLC reports using an integer data item.
So I think the first pattern of setting an existing table to temporary is dangerous and I'm not sure why it still exists?
I have tried a couple of variations of the temporary record to display results on a page and report. First below example
var
TempVend: Record Vendor temporary;
begin
TempVend.Init();
TempVend."No." := '30000';
TempVend.Insert();
TempVend."No." := '10000';
TempVend.Insert();
TempVend."No." := 'blah';
TempVend.Insert();
[b]TempVend.deleteall(true);[/b]
The problem is with table trigger = true , it deletes related records. I have seen recommendations to use above without true such as deleteall() but the problem is by mistake someone else can modify this code to True or I can leave True and actually delete records on the source actual table.
So I prefer creating a brand new table of with:
TableType = Temporary;
Now I have to populate this table and display on a page at run time and if required I can union other tables. Same can be done on RDLC reports using an integer data item.
So I think the first pattern of setting an existing table to temporary is dangerous and I'm not sure why it still exists?
0
Answers
It is a good practice to test the variable to ensure it is temp. You can use ISTEMPORARY() to test the temp variables.
I have had the same issue where I accidentally deleted records because of this, and this is made worst, if there are several developers working on the same problem.
Jordi