Need assistance with SuppressTableRow merge tag

Wow! 2 of my favorite people in 1 thread!!! ​@RobinD I hope everything is great in your world!

Short answer first - try this and let me know if it works: 

<# <SuppressTableRow Select=”((//Pharmacy_Products[1][RBD1 = R90BD1 and RNEGD1 = R90NEGD1]))” Match=””/> #>

I can’t say confidently this will work without having tested, since I don’t have access to your XML and DocGen, but I recreated it with some assumptions. There are several ways we can pull this off though.
___________________________________

Long answer now - You can use AI/LLM tools like ChatGPT with helping create merge tags for you, I’ve found it to be super useful, but sometimes they can set you on the wrong track because they don’t understand the limitations of our CLM tool. Merge tags are built on XPath, so when I talk to ChatGPT, I don’t mention anything about DocuSign and ask them to create an XPath based on the XML from our DocGen form - which is <Params> in the Workflow Activity, as you know it in CLM.

So in this scenario, you are trying to suppress a row based on 2 criteria. So you chose the correct merge tag type - SuppressTableRow!

Here is the shell for that Merge Tag that works with DocuSign CLM. Then the XPath inside of it is what you can customize and talk to ChatGPT about.

<# <SuppressTableRow Select=”(//XPATH INSERTED HERE)” Match=””/> #>

I can ask, based on the following XML (Params in Workflow Activity), can you give me an XPath to match with the following criteria. That prompt can give you something like this:

Then I can go into xpather.com to validate my Xpath provided by ChatGPT is correct (see screenshot)

(//Pharmacy_Products[1][RBD1 = R90BD1 and RNEGD1 = R90NEGD1])

Then I can plug that Xpath ChatGPT gave me, into my merge tag and I get the following!

<# <SuppressTableRow Select=”((//Pharmacy_Products[1][RBD1 = R90BD1 and RNEGD1 = R90NEGD1]))” Match=””/> #>

It might not work first time - but should be close! It’s a little tricky the first time but once you get the hang of it, you can solve every potential merge tag use case that comes your way.