RapidStart un-checking Direct Cost Posting in Inventory Setup

(0) Share

Report

Posted on by Community Member

Hi,
The CustomerSource support doesn't seem to allow me to log this issue, so checking here if anyone has seen this and if MS is aware of this.

After the Direct Cost Posting was suddenly not set in two cases, investigation showed that the RapidStart import un-checks it before import and then re-checks it when done. This is fine unless something happens during the run, client crash or more commonly the users just cancels the import. Then the setting is not put back and you have essentially changed the posting setup.

Has anyone seen this or potential solution ?

Its easy to reproduce this:

1. Using 2017 Cronus (10.0.13682.0)

2. Set the direct cost posting in the Inventory Setup to True

3. Create rapidastart package for item table and export the table

4. Import the excel again

5. Apply data and when it has processed few records cancel the run

6. The Direct Cost Posting is now set to False.

br.,
Hogni H.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Community Member on at

Like (0)

Report

Sorry its of cause Automatic Cost Posting I'm referring to, not direct cost posting.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The code responsible for this is in CodeUnit 8611, ApplyPackage. Now while its easy to comment this or the commit out this must be there for reason - if anyone has knowledge on this please let me know.

br.,

Hogni H.

Was this reply helpful? Yes No
Hannes Holst 5,767 on at

Like (0)

Report

Hi,

Sorry, no answer.

I just want to add that I have experienced the same problem which lead to problems in inventory valuation/trial balance.

The only information I found is that it is recommended to disable "Automatic Cost Posting" during Migration (which is done using rapidstart normally). This code might be some kind of "guarding the unaware"?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for the reply Hannes,

Our partner logged this issue at MS and we got the following answer where this was removed. I'm not sure if or in what update this is changed :

"The code which changes setup is removed since we don’t need that in EMEA. We added some integration events since that is required in an extension from US where they are importing data from QuickBooks. To summarize, for our perspective, it is fair to just remove the code"

br.,

Hogni H.

Was this reply helpful? Yes No
GwaindepyKudah 53 on at

Like (0)

Report

I removed the code from rapid start codeunit

Was this reply helpful? Yes No