Best Practice - OCUSMA need extra field with M3 Analytics

tdouglass

Hi,

I need to bring in the ADVI column from OCUSMA.  It isn't targeted in M3 Analytics.

Is the best practice for me to bring in the Source Again in our custom space and include the field I need in a table like Level[OCUSMA.OCUSMA]  with no Customer dimension (as already in M3 Analytics)

Also, the OCUSMA out of M3 Analytics in source has date range on the connect, and incremental on the relate with no delete keys and no hierarchies.  I am assuming this results in only the changed records when an incremental runs

Tina

vinayak-tayshetye

Hi TD, I have M3A versions from 16.1.9.0 to latest and all of them have all the fields in OCUSMA targeted.
Please check in Dimension space, OCUSMA-ADVI is targeted in M3Analytics with hierarchy Customer.