Answered

Account structure can't be removed due to unposted source documents

(0) Share

Report

Posted on by howalker

1,212

365 will not let me remove an account structure because I have "unposted source documents" but it doesn't tell me what kind of documents (AP, AR, GL, purchasing) or where to look. This is different than AX 2012. I never had a problem detaching a structure in 2012, even in a production environment with lots of transactions. Has anyone encountered this?

*This post is locked for comments

I have the same question (0)

All responses (17)

Answers (1)

Suggested answer

Nagendra Varma K on at

Like (0)

Report

Hi Howard,

You can remove account structure in 365 as well, Seems like you are hitting error may be you are using account structure in posting definition or budget control configuration parameters or transaction which are pending for posting kind of scenario.

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi Howard,

Have you checked the GL inquiry form for the unposted subledger entries?

Are there records pending there?

Best regards,

Ludwig

Was this reply helpful? Yes No
Suggested answer

Mahmoud Hakim 17,887 on at

Like (0)

Report

you can check dimensionattributevaluecombination table , and filter on your account

Was this reply helpful? Yes No
howalker 1,212 on at

Like (0)

Report

Thank you for replying. I don't have budget control set up, so that's not it. I have removed the structure from the ledger posting definition, and that did not help the error. I'm still getting it.

Was this reply helpful? Yes No
howalker 1,212 on at

Like (0)

Report

I have checked. I do not have any unposted subledger entries.

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Howard,

If you can't get this resolved yourself, please contact the MS support.

I have found some similar issues on LCS and the system behavior you experience might simply be caused by a bug.

Best regards,

Ludwig

Was this reply helpful? Yes No
howalker 1,212 on at

Like (3)

Report

Update as of 8 August 2017: Microsoft responded to my support request telling me that this function is working as designed. I replied saying that this position leaves the end user high and dry. They don't allow you to remove / detach an account structure when unposted transactions exist while at the same they don't give you a way to identify the offending transactions. I cannot imagine any accountant on their product team would have signed off on this design change since there will always be an unposted transaction somewhere. AX 2012 did not work this way. I have escalated this with Microsoft because this design change is preventing my client from beginning user acceptance testing. I continue to be baffled by Microsoft's response.

Was this reply helpful? Yes No
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Howard,

Many thanks for this update.

I have a question:

Would you be so kind and post a new idea on the dynamics ideas site by referencing to this thread?

ideas.dynamics.com/ideas

I think it should get a high priority especially if you refer to this thread here.

Many thanks for your support and best regards,

Ludwig

Was this reply helpful? Yes No
howalker 1,212 on at

Like (0)

Report

I posted this idea to Ideas.dynamics.com ideas.dynamics.com/.../ID0002463

Was this reply helpful? Yes No
Verified answer

howalker 1,212 on at

Like (2)

Report

I submitted a support request to Microsoft which got attention. After escalating it, I had a phone call with the Dimensions product team. They agreed that this situation leaves users stuck. This functionality was designed in to 365 in order to prevent data corruption problems that would have resulted if users are allowed to remove / detach an account structure. My complaint was not unexpected. They provided a script that we were allowed to run in a test environment. The script deleted the relationship between a ledger and its assigned account structures. The script did not delete the structure, just the relationship between the two. The product team said they will develop a more long term approach to resolve this problem. They did not commit to any one way. I suspect it will be some type of report to show users where the unposted transactions are so they can be deleted since, in a production environment, users will not be allowed to run a script.

Was this reply helpful? Yes No