I would like to make a request to be able to see all DV tables from the BC Integration Mappings in the New Mappings section without the need to use the AL Proxy Generator (i.e., to use the Integration Table Mappings GUI to view and create this integration). I understand that customizing mappings can be complicated and involve mapping dependent tables first (like mapping Price List and Salespersons before mapping Sales Order), however, BC should notify us of these dependencies before creating the New Mapping. 

A scenario would be creating a custom Sales Order table in DV based off the Sales Order table in BC. This DV environment has no CRM app, so we must re-create them and add relationships to other tables manually in DV. Say we wanted to map this integration, BC should:

1. Allow us to see the newly created custom Sales Order table in DV
2. When we attempt to create a new mapping in BC, it should throw an error (or warning) telling us to create a new mapping and sync to Price List first before proceeding.

I understand we can’t blindly create BC tables in DV and expect them to be mapped at will. For this reason, it would be nice to see BC entity relationships so we an re-create them in DV and faithfully map those tables. This would be the third request – to be able to see those BC relationships so we can mimic them in an agnostic DV environment that doesn’t have CRM.