Advertisement

Ad code

Copy Company and Number Sequence Issue

When it comes to setting up multiple companies, stream lining the process can save you time and effort. One effective strategy is to establish a template company or select a source company to replicate from. 

In this blog post, I won't go through how to use the copy company feature as there are many blogs out there and Microsoft has some good documentation.
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/copy-configuration

What I will explain is an issue I faced when using it. I found that the copy number sequence isn't working as expected. It throws an error when used as part of the copy company.

Number sequence feature:

There are two check boxes for number sequence copy:
  • Copy number sequence - this will add number sequence entities and when run, it will change company references in the staging table before processing to target.
  • Reset to smallest value - this resets the number sequence if it is used back to its smallest value. In most cases back to 0.

Issue:

If you use the V2 entities, you will notice that it will result an error (doesn't do the above behaviour). 

What I would do as a work around, is disable the V2 and use the original entities as they still work.




The reason for this behaviour is that it is hard coded to the original entity staging table name. 


See below how it looks at the constants specified above.



When it comes to setting up multiple companies, stream lining the process can save you time and effort. One effective strategy is to establish a template company or select a source company to replicate from. 

In this blog post, I won't go through how to use the copy company feature as there are many blogs out there and Microsoft has some good documentation.
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/copy-configuration

What I will explain is an issue I faced when using it. I found that the copy number sequence isn't working as expected. It throws an error when used as part of the copy company.

Number sequence feature:

There are two check boxes for number sequence copy:
  • Copy number sequence - this will add number sequence entities and when run, it will change company references in the staging table before processing to target.
  • Reset to smallest value - this resets the number sequence if it is used back to its smallest value. In most cases back to 0.

Issue:

If you use the V2 entities, you will notice that it will result an error (doesn't do the above behaviour). 

What I would do as a work around, is disable the V2 and use the original entities as they still work.




The reason for this behaviour is that it is hard coded to the original entity staging table name. 


See below how it looks at the constants specified above.



When it comes to setting up multiple companies, stream lining the process can save you time and effort. One effective strategy is to establish a template company or select a source company to replicate from. 

In this blog post, I won't go through how to use the copy company feature as there are many blogs out there and Microsoft has some good documentation.
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/copy-configuration

What I will explain is an issue I faced when using it. I found that the copy number sequence isn't working as expected. It throws an error when used as part of the copy company.

Number sequence feature:

There are two check boxes for number sequence copy:
  • Copy number sequence - this will add number sequence entities and when run, it will change company references in the staging table before processing to target.
  • Reset to smallest value - this resets the number sequence if it is used back to its smallest value. In most cases back to 0.

Issue:

If you use the V2 entities, you will notice that it will result an error (doesn't do the above behaviour). 

What I would do as a work around, is disable the V2 and use the original entities as they still work.




The reason for this behaviour is that it is hard coded to the original entity staging table name. 


See below how it looks at the constants specified above.



Post a Comment

0 Comments

Comments