1) different env in the sql code using #pENVexecution# DS parameter
where ('#pENVexecution#' = ' D' and <condition> and <condition2>
or
('#pENVexecution#' = ' P' and <condition> and <condition2>
2) BOM
3) use one copy before sending a DS to a lookup reference to have the real numbers
bug: 11.5.0.2
number of lines of the reference link is wrong!
4) lookup file set vs dataset (for lookups)
lookup file set must have a key, the name of the column (key) must be the same column as source.
differently as per dataset.
5) Json (hierarchical data stage - made with flash)
https://www.ibm.com/support/producthub/ugi/docs/content/SSZJPZ_11.7.0/com.ibm.swg.im.iis.ds.stages.xml.core.usage.doc/topics/examples_jsonstage.html
it uses hierarchical data, examples you can find on IBM website with files provided
https://www.ibm.com/support/pages/node/603441
json_examples.zip
use the web site to validate the json file
https://json-editor.tangramjs.com/index.html
https://json-editor.tangramjs.com/editor.html#/
After opening the assembly editor, you choose Palette to:
AGGREGATE, H PIVOT, HJOIN, REGROUP, SORT, VPIVOT, SWITCH, UNION, ORDERJOIN,
WEB SERVICES:REST, XML PARSER/COMPOSER, JSON PARSER(SOURCE)/COMPOSER(CIBLE)
Output step is the most important, where Mappings tab is used to map the nodes with the columns
Aucun commentaire:
Enregistrer un commentaire