1 Message
Ingesting Description from Salesforce via JDBC
Hi All - I am trying to ingest metadata from Salesforce, including Description of the objects.
From the JDBC Driver documentation I know that IncludeMetadataDescription parameter allows for such action.
Unfortunately I am not able to archive the desired outcome, and when using mentioned parameters I get the following outcomes:
When value =TablesAndColumns – Result: Empty Schema created
When value =Tables – Result: Empty Schema created
When value =Columns –Result: All assets ingested, both ‘Description’ and ‘Description from Source System’ attributes are empty for all assets|
When no value –Result: All assets ingested, ‘Description’ attribute empty for all assets, and ‘Description from Source System’ attribute populated by system message (not actual Description from Salesforce)
Any idea for such weird behaviour?
Community_Alex
677 Messages
•
14.2K Points
3 years ago
@grzegorz.jablonski.murdio.com If you haven’t already, this would be a good candidate for submission to our Support Portal. When submitting, I would reference the URL of this thread.
0
0
jimpine
10 Messages
•
55 Points
2 years ago
@grzegorz.jablonski.murdio.com I’m experiencing this same odd behavior? Was it resolved and if so, how? I was hoping that the latest Salesforce connector would have resolved it. Thanks for any response toward a resolution. I’m using the Edge server for this ingestion process.
1
0
jimpine
10 Messages
•
55 Points
1 year ago
Hello, @grzegorz.jablonski.murdio.com.
For the source description field, we were pulling in some “Label” field from Salesforce. These were unique and semi descriptive, but the prefix “Label” was placed in front of each description and a suffix of “corresponds to this field.”. I’ve reached out to our Salesforce data owner to get any update or clarification on that field and other fields pulled in from the Salesforce. We’ll be looking at adjusting the column mappings if I find that their column metadata isn’t matching up. We did not get to parameter usage in our runs.
0
0