There is currently a stop-gap solution fixing a discovered issue with SQL. So it seems that pulling the database
INFORMATION_SCHEMA will show tables with the format
CRMTableName. This causes issues with
remote.Construct as it verifies that
CRMTableName is the correct name, yet SQL will error as that table does not exist in the schema; it expects
The current solution only fixes the issue for two commonly-used tables, something must be implemted for all tables with that naming format.