Cloud Data Migration: Posting Errors

(0) Share

Report

Posted on by SonnyPawchuk

114

Version: CA Business Central 20.5 (Platform 20.0.45448.46843 + Application 20.5.45456.45681)

Cloud Migration version: 2.7.3

Was able to successfully run the "Run Data Upgrade Now" step back in June-2022, now (Sept-2022) when running this step with the same Dynamics GP source data, status is stalled at "Upgrade Failed", with over 999+ GP Synchronization Errors, Posting Errors.

When drilling into the Posting Errors, The two error are:

(999+ errors) There is a gap in the number series , and
(3 error) Amount must be specified.

All errors seem to be on the GPBANK General Journal batch that the Cloud Migration Tool creates.

Retesting, as a migration preparation step, I set the GJNL-GEN No. Series, the one that the migration created GPBANK batch uses, to allow nulls. Understanding that this should resolve the first error, but not the second error (Account must be specified).

The result is no change in the "Run Data Upgrade Now" results, still 999+ errors.

I can remove the 3 empty account line items and then post the GPBANK batch manually. There are a number of migration created GP General Journal batches that don't post because of this error, by these other batches (Including GPCUST and GPVEND) post without issue. But I am now concerned if there is any other data not imported because of the General Journal posting stoppage.

Even if the data migrated successfully, Cloud Data Migration tool is set to a state of Upgrade Failed and these errors can't seemed to be skipped to allow the tool to finish in a successfully state.

Questions

How can the posting errors be bypassed?

If the errors can be bypassed, can the status be updated to successful?

Any indication if rest of the data migration completed, (through the tool).

Anybody know of any planned Tool hotfix?

See you all at Dynamics summit 2022.

All responses (7)

Answers (1)

SonnyPawchuk 114 on at

Like (0)

Report

RE: Cloud Data Migration: Posting Errors

Update on Cloud Migration.

Cleaning up the CM20200 file worked, and the migration time dropped from 4 hours to 2 hours (Migration time may be dependent on other variables).

Thank you for your assistance Deseree Krumm
SonnyPawchuk 114 on at

Like (0)

Report

RE: Cloud Data Migration: Posting Errors

Hi Deseree,

For today's test I am updating the 3 applicable transactions with the following update script.

-- !!!UPDATE SCRIPT INCLUDED CONFIRM ALL TRANSACTIONS TO BE UPPDATED BEFORE EXECUTING!!!

SELECT * FROM CM20200 WHERE TRXAMNT = 0 AND Recond = 0

UPDATE CM20200 SET DSCRIPTN = 'Void', Recond = 1, VOIDED = 1, VOIDDATE= TRXDATE, VOIDPDATE= GLPOSTDT,VOIDDESC = 'Void' WHERE TRXAMNT = 0 AND Recond = 0
Amit Baru 3,027 on at

Like (0)

Report

RE: Cloud Data Migration: Posting Errors

Hi,

Adding more info-:

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-dynamics-gp

Regards

Amit Sharma

www.erpconsultors.com
SonnyPawchuk 114 on at

Like (0)

Report

RE: Cloud Data Migration: Posting Errors

Good Morning Deseree,

There are three results in that query.

My guess is that these are the same three results shows as zero in the import.
Verified answer

Deseree Krumm on at

Like (1)

Report

RE: Cloud Data Migration: Posting Errors

Hello Sonny, my pleasure and would like you to run the following against your GP database:

SELECT * FROM CM20200 WHERE TRXAMNT = 0 AND Recond = 0

If results are returned, that is bad data in GP that needs to be addressed. For the GPBANK No. Series, that you should be able to get by, but I believe you have bad data somewhere that needs to be addressed. Let us know if you see any results.
SonnyPawchuk 114 on at

Like (0)

Report

RE: Cloud Data Migration: Posting Errors

Hi Deseree,

Yeah deleting the company is part of my steps.

I have been using your forum post as a guide (Great post by the way).

community.dynamics.com/.../changes-to-the-gp-migration-tool-starting-with-version-19-5

My additional steps is that I delete the company in BC and then run the Cloud Migration setup for only one company. Which works for this GP client since they only have a <Test> company and production company.

The process had been working until the latest import Tool version where the Cloud Migration step now asks to import Item, Customer, and Vendors Classes along with identifying historical year. My functional analyst has noticed bank transaction changes, the the tool generated GPBANK batch is the one erroring out.

Current snippet of process document using your post as an initial guide.

I am going to rerun the migration Thursday (to test some other pre/post migration processes). Not sure if I will retry the test to change the GJNL-GEN No. Series to allow nulls or not. I will also check out your provided GP Migrations links.

If the error persists after Thursday's update. There will probably be a support ticket created by the client.
Suggested answer

Deseree Krumm on at

Like (0)

Report

RE: Cloud Data Migration: Posting Errors

Hello Sonny.

When you attempted to run the migration again in September, did you delete the company in BC before you began? I believe these errors are voids and the data condition is fine as when you migrate from any source, you should not need any kind of setup in BC Saas to get the data to flow. I would highly recommend deleting the company in BC and run thru the migration process again. Once you run the 'upgrade Now' option, you should never go back and attempt to migrate again. Think of that step as the point of no return without starting from the beginning. If you do this and you still get errors, I would submit a support ticket so we can take a look. I would also like to call attention to a great resource for all things GP migrations which can be found here.

Thank you,

Warmest Regards,

Deseree Krumm| Support Escalation Engineer