EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB45492: Updated fields in SalesForce.com are not updated after Update Structure is performed successfully in Warehouse Catalog in MicroStrategy Developer when using SalesForce as a data source.


Community Admin

• Strategy


New fields are created or modifications are made to existing fields in SalesForce.com, but the changes do not appear in MicroStrategy Developer after Updating Structure on the specific tables that should reflect the changes.  In addition, the changes do not appear when viewing the table structure from Warehouse Catalog, Graphical Architect, or DB Query Tool in MicroStrategy Developer 10.x

SYMPTOM:
New fields are created or modifications are made to existing fields in SalesForce.com, but the changes do not appear in Strategy Developer 10.x after Updating Structure on the specific tables that should reflect the changes.  In addition, the changes do not appear when viewing the table structure from Warehouse Catalog, Graphical Architect, or DB Query Tool in Strategy Developer 10.x
CAUSE:
The cause of this issue appears to be the result of the default setting for the Create Database option for the DSN used to connect to SalesForce as a data source. 
The default setting for Create Database is set to "2-NotExist", and if this is set, then no new database will be created if the driver can detect an existing database. 
If an existing database is found, and used, then most likely these changes will not be reflected.
ACTION:
Set the Create Database setting to "1-ForceNew" by configuring the SalesForce DSN in ODBC Administrator. 
When 'Create Database' is set to "1-ForceNew", then the driver will delete the existing database if it exists, and will create a new database for each new connection. 
As a result, a new database is created which should have the updated fields. 
After the new changes have been successfully shown after using this setting, then it can be set back to "2-NotExist", otherwise every time a new connection is made to the data source, it will delete the existing database and create a new one.

ka04W000000uGD1QAM_0EM440000002CZW.png

 Contact Strategy Technical support if the issue persists after performing this step.
KB45492


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

December 31, 2018