I have the following situation:
A customer is moving from NAV2017 to BC SaaS, we're providing them with RapidStart packages to port their data. I would like to send them .rapidstart files with the correct metadata: tables and fields.
The problem now is that when I export some packages, the table Config. Media Buffer is automatically added and exported. This table doesn't exist in NAV2017, so the customer gets an error.
I did enable "Exclude configuration tables", which didn't work.
I have a potential workaround: Create a RapidStart package containing the metadata for the other RapidStart packages. But I'm still curious why this table is needed and how to prevent this behavior. I'm guessing it has something to do with the way Images and the like are stored in BC?
Would love to hear your ideas!