Use custom listing name for the custom listing schema
If you are using a visualization tool to view data through custom listing schemas, set this profile to Yes to generate the secondary schema name with the same name as the custom listing. Using the name makes it easier for users to pick the listing they want to view in the visualization tool. The visualization tool can also query for the custom listing name instead of the ID. For example:
select * from BA_INF_CL_DEV.CLTEST;
where BA_INF_CL_DEV is the custom listing schema and CLTEST is the custom listing name, instead of:
select * from BA_INF_CL_DEV.QB_3254235_V;
where QB_3254235_V is the generated ID.
If set to No, the secondary schema created for the custom listing is named with the map ID generated by the system and visible only in the LSH work area.
Parent topic: Set profiles to determine system behavior