5,457
Since it looks like it is from the same XYZ DB but a different company we should be able to use the same package???
The new instance is just a new company that will reside in the xyz database.
Can we use same package for the same db
We need to pull account related information into CRM from this new NAV instance. I don’t want to build new packages unless it is absolutely necessary as maintenance becomes an issue
*This post is locked for comments
You are going to end up with either
a) 1 very complex ssis package with a lot of duplicated functionality or as it needs to handle both NAV instances and the CRM system
b) 2 simple SSIS packages based on a standard template where the only thing that differs between them is the connection to the NAV instance.
I would be aiming for the second approach as it provides both a more sustainable long term approach and a shorter development plan.
If the data is going from NAV to CRM (and not the other way around) you will be able to use the same template across both instances. However you will need some flag in the CRM system to identify which NAV system the customer belongs to which will mean you will need to add a flag attribute in CRM for the system and find a means (within the SSIS configuration file) to ensure the SSIS package populates that flag within the appropriate details...
We need to pull account related information into CRM from this new NAV instance. I don’t want to build new packages unless it is absolutely necessary as maintenance becomes an issue . Since it looks like it is from the same xyz DB but a different company we should be able to use the same package – just add unions for new company in selects from NAV?
May be we need to add fields into your staging/temp tables for company so we know which account is for which company? we might have to update the new fields for existing data with xyz company?
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
52
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
