Content Comparison

...

It’s recommended that you create a projection. The projection will allow you to point to another base view if your data source changes later on. If performance of the projection is inadquate, consult the Data Strategy team on enabling caching for the projection.

Diagram

Salesforce

https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/creating_data_sources_and_base_views/salesforce_sources/salesforce_sources

Parameterizing Base URL

Denodo doesn’t natively support parameterizing the Salesforce Base URL when deploying via Solution Manager. This results in the value in DEV being statically propogated to STAGE and PROD via VQL. To parameterize Base URL do the following:

1. For any revision where a Salesforce connection is being deployed either by itself or as a depedency (Include VDP Dependencies checked), download the VQL for that revision and put the following in place of the BASE_URL line for the Salesforce connection VQL (replacing VDB_NAME and SF_CONNECTION_NAME with your VDB name and name of the Salesforce connection).

   Code Block
   BASE_URL = '${databases.VDB_NAME.folder.01-base_layer.folder.01-connections.datasources.salesforce.SF_CONNECTION_NAME.BASEURL}'

2. If this is your first time deploying, or you’re looking to update properties, perform validation against STAGE and PROD for your initial revision. This is only needed to allow faster copying of certain properties from DEV. Delete the initial revision after this to avoid risk of deploying it.

3. Create a second revision using the edited VQL file from step 1

4. Validate the second revision. You should only need to input the BASE_URL value at this point if you performed step 2.

5. Deploy your second revision.

Repeat these steps any time you deploy a Salesforce revision,

Flat Files

Box

In Denodo, you can query files in Box by creating connections and base views for individual files.

...