Small and medium business | Business Central, N...

Error while uploading Configuration package

(8) Share

Report

Posted on by Hatimali84

564

Hi all,

I am getting this weird error message when trying to import a config package for FA Ledger Entries.

Your licence does not grant you the following permissions on TableData 5601 FA Ledger Entry: Insert. To view details about your permissions, see the Effective Permissions page. To report a problem, refer to the following server session ID: '35059'

I have super user permission and there is no company restriction.

I have checked all articles on Internet but none of them apply or resolved my issue.

I have also checked that my environment is not a trial environment.

Can anyone help or have encountered this issue.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (11)

Answers (0)

Suggested answer

Gavin 2,508 on at

Like (3)

Report

Hi,

This is likely because you shouldn't import directly into Ledger Entry tables. (I'm not even sure you can)

You should import into the Journal line table and then once the journal has been import you post the batch to update the Ledger Entry tables.

Therefore if you are importing a Fixed Asset Journal and you want it to update the GL then use table 81 in your configuration package. This is because the "Fixed Asset G/L Journal" page uses this table. (see below)

If you want to import into the Fixed Asset Journal and the journal not update the GL you would tend to import into the "Fixed Asset Journal". Therefore you would use table 5621 in your configuration package.

After you have imported into the relevant journal you can then post the journal to update the Ledger Entries.

Hope this helps

Thanks

Gavin

Was this reply helpful? Yes No
Suggested answer

Sumit Singh 10,193 on at

Like (5)

Report
In Dynamics 365 Business Central, even if a user has the SUPER permission set, they are still bound by the limitations of the license. According to Microsoft's official documentation:
"SUPER can read, use, update, and delete all data and all application objects in the scope of your license."
— Microsoft Learn: Special Permission Sets
This means that:

TableData 5601 (FA Ledger Entry) is a protected system table.

Insert operations on this table are not allowed directly, even for SUPER users, unless the license explicitly allows it.

This is by design — FA Ledger Entries are system-generated through FA Journals or depreciation runs, and cannot be manually inserted via config packages or direct data manipulation.

🔒 Why This Happens:

Business Central enforces data integrity by restricting direct writes to critical tables like ledger entries.

These tables are typically write-protected to prevent corruption or bypassing business logic.

✅ Recommended Actions:

Use FA Journals:

Instead of importing directly into FA Ledger Entry, import your data into Fixed Asset Journals and post them. This will create the ledger entries properly.

Avoid Direct Table Imports:

Configuration Packages are not suitable for system-generated tables like 5601.

Raise a Support Ticket (if needed):

If you believe your license should allow this (e.g., in a highly customized or on-premises scenario), contact Microsoft Support with:

Table ID: 5601

Error Message

Server Session ID: 35059

Was this reply helpful? Yes No
Suggested answer

Andrés Arias 4,190 Super User 2025 Season 2 on at

Like (3)

Report

Hello,

I am not sure what you are trying to perform, but it should not matter directly to asset ledger entries.

If we import Balances, it would be table 81 or 5621.

Hope I can help.

Regards,

Andres

Was this reply helpful? Yes No
Suggested answer

Ahmad Subhani 585 on at

Like (2)

Report

Hi,

This is the Permission Error.

1- Go to User ID.

2- Check the Permission Sets.

3- Go to that specific Permission sets and add the line of "TableData 5601".

Mark the Answer as Verified if this is Helpful.

Was this reply helpful? Yes No
Suggested answer

Mansi Soni 8,907 Super User 2025 Season 2 on at

Like (5)

Report

Hello,

This error typically occurs because Table 5601 (FA Ledger Entry) is a system-controlled table, and even users with SUPER permissions cannot insert records into it directly entries must be created through standard FA processes like acquisition, depreciation, or disposal. Config packages cannot be used to import into FA Ledger Entry, as Business Central restricts direct inserts to maintain data integrity.

To resolve this, import through standard Fixed Asset journals or acquisition documents rather than attempting to insert ledger entries directly.

Hope this answer will help you!

Regards,
Mansi Soni

Was this reply helpful? Yes No
Suggested answer

RockwithNav 8,635 Super User 2025 Season 2 on at

Like (2)

Report

We should never ever do any insertion directly in any of the ledgers my friend. Ledger should always be system driven.

Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 8,760 on at

Like (2)

Report
Hi,

That error message about lacking insert permissions on TableData 5601 (FA Ledger Entry) can be confusing, especially when you’re a super user and working outside a trial environment.

Here’s what’s possible:

Even with SUPER permissions, BC enforces table-level restrictions for certain system tables like FA Ledger Entry. These are considered protected posting tables, and direct inserts via configuration packages are blocked by design to preserve data integrity.

The FA Ledger Entry table is read-only for imports — you can’t insert records manually or via config packages. Entries in this table are created only through posting flows, such as fixed asset journals or acquisition postings.

If your goal is to migrate FA data, you should import into Fixed Asset and FA Journal Line tables instead. Then post the journal to generate the FA Ledger Entries properly.

You can confirm this behavior by checking the Effective Permissions page, but even SUPER users will see insert blocked for certain tables due to system-level constraints.

Helpful references:

Configuration Package Error Handling – Dynamics 365 Lab
Importing Data Using Config Packages – Valentin Castravet
Correcting Data Import Errors – BC Insight
Warnings and Error Messages – Microsoft Learn
FA Ledger Entry Permissions Discussion – Dynamics Community

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

Was this reply helpful? Yes No
Suggested answer

Teddy Herryanto (Th... 14,284 Super User 2025 Season 2 on at

Like (2)

Report

All ledger entries are "protected" tables. It means you cannot directly insert/modify/delete the record inside it even if you have the permission to it.

The only way to push data to it is to specify indirect permission inside your code.

An example is the posting routines. The indirect permission is applied to the code that performs the posting.

Inserting directly to ledgers are not recommended, because when you post, a lot of tables get involved. When you post Fixed Asset Journal, it's not just FA Ledger Entry table is involved. This is why you should always push import to journal and post it.

If you push directly to the ledgers, things will break if you miss one of tables.

In summary, don't do it.

Push to journal and post it.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,597 Super User 2025 Season 2 on at

Like (1)

Report

Hi, I mentioned this in the post below, I hope it can give you some tips.

Dynamics 365 Business Central: Can we insert/modify/delete posted data (Posted Documents & Posted Entries) via AL???

https://yzhums.com/54657/

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

Hatimali84 564 on at

Like (2)

Report

Hello Everyone!!

Thank you for all the responses. We cannot directly post into Ledger. The way to move forward we will add the lines to the journal and then post from there.

It was very helpful from all of you to guide on this as I didnt knew we cannot add directly to Ledger table.

Regards,

Was this reply helpful? Yes No