3774251 - story report error "we are unable to find the selected table or column in the database" when creating report on an object from Custom schema

• Adding a related entity from custom schema causes the query to fail.
• Error message: "We are unable to find the selected table or column in the database."

• Data Modelling - Module & Entity Data Issues

1. Create a Story report.
2. Drag and drop any object from Custom schema
3. Select any field
4. Preview the Story report and observe the error.

• A custom schema in the destination instance had the same name as a previously used schema except for letter case (case-only difference). A lingering backend reference to the earlier casing caused the system to treat them like duplicates, leading to the "table or column not found" error when building the query.

1. Review custom schemas names across all relevant instances (for example, source and destination after a refresh) and identify any case-only duplicates.
2. Align and keep custom schema names synchronized across instances to prevent case-only naming conflicts, especially after instance refreshes or configuration transports.

"Unable to find the selected table or column in the database" error due to 127 character limit for custom MDF object

story report, unable to find the selected table or column in the database, custom schema, case sensitivity, schema name conflict, duplicate schema, report object configuration entity, story preview error, people analytics, data modelling, table or column not found, custom schema, instance refresh , KBA , LOD-SF-ANA-SAC-DAM , Data Modelling - Module & Entity Data Issues , Problem