Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | All TechTalks | Architecture Insights
I'm working on migrating the Forecast Sales table. The only issue (as far as I know) involves the "parent-child" relationship that exists between the records (the child's Expand ID is the Rec ID of the parent).
I already have a custom method for generating the Expand ID, however when I run through the migration process, every Expand ID is 0. It is entirely possible that the code in my method could be wrong, but I've been thinking that I might have to migrate the data in two steps: import "parent" records first and "children" records second.
Has anybody had success with importing ForecastSales in general or with importing in multiple steps?
Thanks in advance.
Are you importing using X++ or another method that is "within AX"? If so, the expansion of the parent into children should happen automatically as part of the insert()/update() code on that table. I think this behavior only occurs when the Active flag is set on the parent.
If you are importing directly via SQL or another tool, you should know that ForecastSales is not the end of the story. Records insert into ForecastSales generate records directly into ForecastInvent, which is the foundation for most Master planning forecast analysis. In other words, a single "inside AX" insert into ForecastSales can result in many records in both ForecastSales and ForecastInvent, but all of it is fully automatic.
Please elaborate further on your import process.
I am using the Data Import/Export Framework tool.
My issue specifically is this: The records seem to import correctly all the way into the Target table (ForecastSales table), however when I open the table in the AOT, I notice that ExpandID/RecID relationship between the parent/children records is missing.
Is it possible that I have to import records into the ForecastInvent table as well?
To anybody else who also comes across this problem:
In the end, you do need a custom method to set the Expand ID appropriately. However, Brandon's point about the ForecastInvent table is also important. There is a method initFromForecastSales that populates ForecastInvent automatically when entering data through the AX Client interface into ForecastSales. For whatever reason, the ForecastInvent table was not being updated when importing using the DMF tool. As a result, I had to write a little block of code in my custom method that called that 'init' method.
I'm working on importing the sales forecasts and wanted to check on your approach to the custom method for the DMF process. Did you write something at the table level or DMF classes.
Can I please have your direct email if possible.
Hi Brandon ,
I am working on importing data into forecast sales by using DIXF, but i'm facing a situation, after importing data it is visible in the table but not in the demand forecast sales Form. can you help me in this regard.
Thanks in advance,
Do you have records in ForecastSales, but you can't see them in the Demand forecasting form?
The ForecastSales form has an inner join to the InventDim table. On your records, do they have an InventDimId? Does this InventDimId exist in the InventDim table?
Also note that you should also be getting records in the table ForecastInvent. Are those being created by the import?
Business Applications communities