What happened is the following, I exported 5 tables with Ledger Entries for use in Excel, it turned out that the first table held the data from the table, as expected, but the 2nd and later tables showed no data. Instead it showed just one line: the number of the table under Entry No. and in the column next to it the name of the package.
After thinking I had found a bug and contacting MS about, I was told by support that it's actually a feature.
Up to and including BC15, when exporting (Customer, Vendor, Bank, Employee, etc.) Ledger Entries, BC did what it was asked to do and exported the data from the tables indicated.
After BC15, however, there was a change. Apparently, due to importing into those tables not being allowed, it was decided to limit the export of those tables.
It remains unclear why exporting data from 1 Ledger Entry table in a package still works as normal and including multiple tables in a package still results in the output of at least one Ledger Entry table, but not the others.
The official documentation states about this: You cannot import data to tables that contain posted entries, such as the tables for customer, vendor, and item ledger entries, so you should not include this data in your configuration package.
Source: https://docs.microsoft.com/en-us/dynamics365/business-central/admin-how-to-prepare-a-configuration-package#tables-that-contain-posted-entries
But doesn't mention any limitation on exports. It seems to me that MS was a bit overzealous in limiting this Configuration Package functionality.
This can easily be reproduced: Include only table 25 in package and export. Now include tables 21 and 25 in a package and export. Compare the results.
I want the full export functionality back. How do other people feel about this?
