Today, we are pleased to announce that we have improved the way that users can view Namara data in real time on their compatible .NET, SAP or Salesforce-based services. We have utilized our own platform’s Project functionality to allow users to quickly load in more data sets without having to perform extra authorization steps.
As an example, we will walk through the Namara integration on Salesforce.
After logging into your Namara account, click on your user icon in the sidebar (bottom left of the window) and select Account Settings. Then select the API Key tab.
You will need to create an API key if you have not already done so.
Have an open document available and paste your API key in there. You will need to access it a few times as well as keep track of a few other values, so keep it on hand.
For this example, I’m going to create a fresh project and add some new data to it. Below, I have created a sample project that I will use for this walkthrough.
If you already have a project that you would like to view, feel free to use that instead.
For this example, I’m going to use the Heritage Properties data set published in the Hamilton, Ontario open data portal. I start by browsing open data in the Marketplace, and searching “Heritage Properties Ontario”. I can quickly add these to a project by expanding the data set preview and selecting my new project.
When viewing your project, your url should match a pattern like this:
To start out, I want to make sure that I know the current versions for both of my data sets. I can find this out by clicking on the data set card to get to the table view, then clicking on the API Info tab.
I will make note that my data sets are at versions “en-0” and “en-1” respectively. Because Salesforce requires a static set of properties to view OData sources, we must pin our OData adapter to a specific version of a data set. (refer to our API Docs for more information about data set versioning.)
Now we need to set up our OData meta attributes that Salesforce will use to build external objects. Navigate back to the Project view and click on the cogwheel icon for each data set to edit the Project Item settings.
Once this is set up, you can quickly check to make sure that your data is being registered by the Namara OData adapter. Using the IDs that I’ve saved from earlier, I can view in a browser:
We can see from the metadata manifest that it’s registering both Hamilton and Brampton houses as entities and is picking up their properties. It’s also included our activated Project Items as metadata for the Project OData service.
On your Salesforce Lightning dashboard, access “Setup” in the top toolbar.
After arriving at the settings page, either enter “External Data Source” in the Quickfind bar, or navigate to Data > External Data Sources under the “Administration” header.
Click “New External Data Source”, and complete the form for your project.
Here, I have called the data source “Namara Heritage Homes”. I have selected OData 4.0 as my connector type (note that OData 2.0 is not supported by Namara).
The url that I provide is the same as the metadata manifest URL that we built back in step 3. Adjust the other parameter settings to match what is shown here.
Since we are authenticating by API key, we set authentication by User level. The username that you choose does not matter but the password field must be your Namara API key.
Once you have completed this form, click “Save”. You will see the “Validate and “Sync” button on a successful save, but will be unable to complete this action at this time.
Go to your personal settings and add a new Authentication for the external system.
In the sidebar, navigate My Personal Information > Authentication Settings for External Systems. Click on the “new” button and set up the authentication for the new Namara data source that you’ve created.
Search for the user and set up their credentials using the API key. Please note that this assumes that you are the user and you are using your own API key. This can be set up on behalf of another user who is a member of your Namara Project. It can even be set up using their Project API key. (To learn more about how Namara lets you collaborate on data projects, check out our Features Pages.)
Once you’ve finished authorizing this user, save the form. Navigate back to our External Data Source by clicking the link provided.
On this page, select “Validate and Sync”. After a moment, Salesforce will have received and read the metadata document. We are now provided with Data Sets that we can view as Salesforce External Objects.
Now select the Data Sets that you would like to view and click “Sync”.
If I go to my external objects view I should see that these have been added.
Go back to the first settings/setup panel that we were on. Search “tabs” in the quickfind bar or navigate to User Interface > Tabs.
Create two new custom objects tabs for our two house data sets.
If I were to add additional Heritage Home data sets to my project, I would only have to activate those for OData inside of the project, and then re-synchronize the data source to pick up the new external objects.
When it comes to doing something difficult, whether it’s building a business or climbing Everest,…
A career in tech has never been more attractive. Companies of every size are champing…