Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
I’m working with Data Migration Framework Beta 2 with Dynamics AX 2012 R2 and SLQ Server 2012. I have two partitions (Initial & test). In Initial I have only the DAT Company.
Connected to the “Test” Partition I import to the staging tables the demo file “UnitOfMeasureEntity_Basic.txt” and it works correctly (“6 records inserted in staging”). When I go to “Execution history” and click in “View staging data” no records are shown and “Copy records to Target” will not work (“0 records inserted”).
If I make the same test in Partition “Initial” then it work correctly and the records are inserted in Target tables.
How I explain to DMF I’m working with partition other than “Initial”?
Where you ever able to overcome this issue? If so, please share how.
With DMF 2.0 and R2 (w/ multiple partitions), it seems as all records are imported to staging table in initial partition regardless of which partition the DMF import is initiated from.
Thanks in Advance
The new version of the Data Migration Framework (Data Import\Export Framework) works correctly with more than one partition.
Most likely the previous version of DMF didn't have partition as part of the schema in the SSIS packages, and therefor it could not distinguish partition in the data flow.
I thought your network account determined which partition you were in. A user - Admin aside - cannot be in more than one partition.
Users can be in more than one partition, but you can only have one "default" partition. You can define "active" partition on a client shortcut, a service context object (WCF) and so on.