DMF - The account type (Project) selected is not supported

(1) Share

Report

Posted on by Zuk

Hi All,

do you have any idea why when trying to import a General journal with DMF I receive this error

The account type selected is not supported.

The account type is Project, the purpose is to import an Expense journal.

Is that related to the project category field that is not present in the entity strcture as visible field?

Best regards.

I have the same question (0)

All responses (8)

Answers (1)

André Arnaud de Cal... 300,846 Super User 2025 Season 2 on at

Like (0)

Report

Hi FBA,

Can you confirm if you are using Dynamics 365 or Dynamics AX 2012?

Was this reply helpful? Yes No
Zuk 53 on at

Like (0)

Report

D365 latest version

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 300,846 Super User 2025 Season 2 on at

Like (0)

Report

Hi FBA,

In Dynamics 365, you can use the Project expense journal header and Project expense journal lines entities for this purpose.

Was this reply helpful? Yes No
Zuk 53 on at

Like (0)

Report

Hi Andre,

thank you for your reply.

At the moment the requirement is to use the general journal since there are exceptions in the imported file and not everything in it can be manage as a proj expense. Given that, I would like to understand why the system returns this error during import with data management.

Best regards.

Was this reply helpful? Yes No
Verified answer

Alireza Eshaghzadeh 14,672 Super User 2025 Season 2 on at

Like (1)

Report

HI FBA,

You cannot import project transactions via "General journal" entity in DMF.

You can either follow Andre's suggestion or use Excel add-inn (Open lines in Excel > Project expense journal)

Was this reply helpful? Yes No
Zuk 53 on at

Like (0)

Report

Thank you all,

we found a limitation of DMF with some account types and we decide to develop a workaround. Best regards.

Was this reply helpful? Yes No
Rich 326 on at

Like (0)

Report

Andre Arnaud de Calavon
In Dynamics 365, you can use the Project expense journal header and Project expense journal lines entities for this purpose.

Has anyone used these entities in combination whilst generating the journal numbers from the configured number sequence please? Changing the Project expense journal header field mapping for JournalBatchNumber to auto generate gets the header record in, but there's then no way of relating the lines to that newly created header that I can see. I think the answer is probably to use the composite entity Project expense journals, with just the header mappings set to auto generate the journal batch number, but that whilst that works through the UI, it doesn't seem to be supported by the packaging manifest file

Was this reply helpful? Yes No
Suggested answer

Rich 326 on at

Like (0)

Report
As a follow-up to my post in February, the Project expense journals composite entity is the way forward, with two nuances (discussed with MS support, they're looking at where this can be covered in documentation) when including in a packaging zip file (particularly important for DMF REST API import)

The JournalBatchNumber field must be mapped to a field present in the input data file, but then AutoGenerated (to effectively ignore the input value)

The composite entity must be the only entity in the input package

Was this reply helpful? Yes No