Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I think a normal set analysis may also return the wanted result, maybe:
only({< EmpUserID = {"$(=right(osuser(), 8))"}>} BUSINESSUNIT)
If you load the User-BU mapping a second time as a normal (distinct) table you could query the information - either directly to the field if there is only a single record when if the same where-condition could be applied or by multiple values with an expression like:
fieldvalue('BUSINESSUNIT', fieldindex('EmpUserID', right(osuser(), 8)))
load the User-BU mapping a second time as a normal (distinct) table you could query the information. Are you talking about a partial reload?
Appymap and its partner Mapping Tables only is active while loadscript is running. When the script ends then all Mapping tables are dropped for optimization reasons so indexing is also completed.
That is important for consideration on scripting planning as you can drop tables anytime, but a MAPPING table is always there until the end. Larger mapping tables does affect performance as well.
I hope this helps.
No, it hasn't any relation to partial/incremental measurements else just loading the data into the data-model.
Marcus, when I execute the fieldindex function with my ID for example returns the number 1000 which when feed it to the fieldvalue function returns NULL.
We have 1040 distinct ID's tied to 22 BU's in the distinct load table. I think that is why it returns a Null.
Any ideas?
I think a normal set analysis may also return the wanted result, maybe:
only({< EmpUserID = {"$(=right(osuser(), 8))"}>} BUSINESSUNIT)