That's the thing!
The moment that field shows up in the database the whole functionality goes down, so the error shows up and then no table is available to be selected, no column to select/deselect.
I would gladly contribute to the suite project, but I sense that's only available for internals.
After generating the script for the entire database and running each piece individually I stumbled upon something I concluded is not supported by the framework:
CREATE TABLE [ASSET_HIERARCHY](
[ASSET_LEVEL] [hierarchyid] NOT NULL,
) ON [PRIMARY]
There are official libraries that adds support for this MS SQL type:
Can I send a .dacpac privately to an email address? :)
When using ABP Suite Load Entity from Database functionality, it looks that it does not support some schema or table names.
The test case has the following [schema].[table] format across the whole database: [SOME_ASSET_DATA].[SOME_SYSTEM_KEY_MAPPING].
Would this kind of format be problematic?