Hi Felix, You can do it either of 2 ways1. Using Recipient as Filtering
Dimension and using 'Don't exists such as' query on broadlogRcp. Below
screenshot2.Starting BroadlogRcp as filtering dimension and than
changing dimension back to recipient. I prefer option 2 as option 1 is
sub query execution and sub queries are know for there performance
hit.Let me know if you need more details on any of these options.
Hi Zeila, It is not possible with UI. But, if you have good
understanding on XML than you can do it by following below steps. 1.
Right click on workflow and select "Edit xml source ...."2. Look for
your split activity. 3. look for XML code for existing tab, will look
like this4. Copy and paste the code and save the XML. PS: This is not a
preferred route to do it, as it will require playing with XML code and
possibility to corrupt your workflow if something went wrong.
Hi Felix, Seems like your seniors are messing around with you I have
read all the records from srcSchema and try to get attribute details.
Hi Chandni,You have to define revCardinality ="Single" for direct access
of this data in delivery. below is the code
But, I think it might create a issue for you. You have defined
brCode as primary key for you Br_data schema, by due this you are
defining that each and every recipient will have different brCode,
recipient can't share br Code. Adove code will define 1-1 cardinality
between Recipient & BR_Data.If multiple recipient can share same br
code, than you need to define link with below c...
Hi, Can you please also let us know the Cardinality between recipient
and BR_Code schema ? It might be to do with the cardinality, if you have
1-1 or N-1 cardinality from Recipient to BR-Code you can use it directly
it in delivery. Otherwise you to enrich it using enrichment activity
first and than use it as targetdata in delivery. Also, make sure you use
correct link name also. Regards,Ankur A.