Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have configured a number sequence for auto-generating the next numbers with prefix of V- while creating the vendor record manually. It works like a charm.
But our client also imports vendors on weekly basis and while importing the vendor records on weekly basis the data entity should not consider the number sequence and use the vendor number from the Excel file. What can we do to configure this scenario.
- Vendor manually created use number sequence
- Vendor imported via Excel, ignore the number sequence setup.
Currently we disable the number sequence and then push the file manually, but this is not sustainable model and would like to understand our options. Thanks in advance
Out of the box there is no other solution available than the way you are currently using. We had a similar topic in the past with AX 2012 and solved it by a modification.
making number sequence manual is the option, you could write a routine/job to keep switching and could also connect with vendor import data entity to auto execute/trigger
Another approach that does not make use of data management is electronic reporting for the import of your vendors.
This can be realized by adding a file on SharePoint and setting up an import model that regularly takes the file and records and creates the vendor accounts. Compared to the data management approach you are more flexible and have more options how to import data.
The disadvantage is that this is a completely different tool and consequently requires some additional configuration/setup.
Yet, it might be worth having a look at it if you cannot get this fixed with the data management.
Cancel the VENDORACCOUNTNUMBER field validation in the vendors v2 entity.
Thank you Mattguo - This worked. The only catch is now system will not do duplication on the vendor number field and will try to append the information on the existing record. Which is fine and I can work with the client on this.
Thank you all for your guidance on the matter.
This is a downside of having two systems generating numbers. To avoid this, you can better have a distinction in numbering by e.g. a prefix or total other number ranges.
If the reply from Mattguo was helpful, would you mind to mark his answer?
Another option to explore would be setting up a shared number sequence and then set it up per vendor group. See if you can leverage multiple vendor groups.. one for AX and one for integration.
Thanks Satish. Yes - this is a good option too. I will work with my user if they agree to do this. Only downside is they will have to duplicate the vendor groups which is not a bad option.
Business Applications communities