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
RapidStart Services: Processing sequence
pauld
Member Posts: 21
Hi all,
We made base configuration to our liking, validated and exported it.
Now we created a new firm and imported the new package.
It works quite well. However there are a few tables that give an error.
These are mostly related to the processing sequence.
In other words one table gives errors because its master table it not imported yet.
Should we move these dependent packages to a separate package or can you influence the processing order within a package?
Or are we going at this from the wrong angle
?
Cheers,
Paul
We made base configuration to our liking, validated and exported it.
Now we created a new firm and imported the new package.
It works quite well. However there are a few tables that give an error.
These are mostly related to the processing sequence.
In other words one table gives errors because its master table it not imported yet.
Should we move these dependent packages to a separate package or can you influence the processing order within a package?
Or are we going at this from the wrong angle
?Cheers,
Paul
0
Comments
I assume you can't take infuence on the sequence of how tables are processed during rapidstart package import. The tables are listed and processed in the package by their sequential table ID.
Moving tables with data dependencies to a different package and import this one as a second step might be one option.
Also, you can try to re-apply data from the tables of the package you've just imported but which had been processed with errors again. Open the package, identify and select the table with relational errors and from the table menu, run Functions / Apply Data.
If the errors were caused by relational data not being available during the import, these should now being processed successfully.
You might also check the field options on specific tables. Try running your import with Validate Field unchecked for those fields of a given table causing trouble due to their table relations.
Hope this helps
Andrew T.
Thx for your reply!
Good to know I didn't oversee a best practice here.