Hello @Christèle,
Thank you for reaching out, and welcome to the Docusign Community! I appreciate you bringing your question to this Community.
I received a response from our internal team. Last week, an update was implemented that now uses the face value for the picklist. If the picklist is being used for conditions, these conditions will need to be updated to use the face value.
Additionally, for fields such as "SBQQ__Account__r.Payment_Method__c" which are lookup fields, the logic has recently been adjusted. Instead of matching by the label name, the system now matches by the API name. Please ensure that any conditions referencing these fields are updated to use the correct API name to resolve related issues.
I hope you find this helpful. If you believe this response effectively addresses your question, please click “Select as Best” to help other users with similar questions and locate it more easily. Should you require any additional assistance, feel free to reach out. Thank you!
Best regards,
Jenny | Docusign Community Moderator
"Select as Best" below if you find the answer a valid solution to your issue.
hello @Jenny.Martin
thank you for your reply
I’m sorry but I made a mistake
My problem is about SBQQ__Account__r.Payment_Method__c" field where no information is displayed and for /SBQQ__Quote__c/Tech_Payment_Terms__c where I have no display problem.
Can you help me more ?
Regarding
Christèle FOUCAULT
Hello @Christèle,
Yes, with SBQQ__Account__r.Payment_Method__c”. The system has shifted from matching based on label names to using API names. To address related issues, make sure to update any conditions referencing these fields to utilize the correct API name.
Best regards,
Jenny | Docusign Community Moderator
"Select as Best" below if you find the answer a valid solution to your issue.
Hello @Jenny.Martin
Thank you for your reply.
if I understand correctly, I have to replace all my label name with the api name
for exemple
chèque by 1
Virement bancaire by 2…….
but do I have to put a ‘’ or a <> or nothing between Match="1" /> #> Chèque<# <EndConditional/> #>
Is there any explanatory documentation?
Thank you for your help
Regards
christèle FOUCAULT
Hello
I've solved my problem
for my French models, I've replaced the Api name by the value (in English in my salesforce organization)
<# <Conditional Select="/SBQQ__Quote__c/SBQQ__Account__r.Payment_Method__c" Match="Pay Check" /> #> Chèque<# <EndConditional/> #><# <Conditional Select="/SBQQ__Quote__c/SBQQ__Account__r.Payment_Method__c" Match="Bank Transfer" /> #>Virement bancaire<# <EndConditional/> #>
and
for my English models, I've replaced all the Condition select fields with only the field
<# <Content Select="/SBQQ__Quote__c/SBQQ__Account__r.Payment_Method__c"/> #>
Sincerely
Hello @Christèle,
Thank you for the update. You can mark your answer as the "Best Answer
" by clicking “Select as Best”. It helps other community members who might have similar questions. Thank you!
Best regards,
Jenny | Docusign Community Moderator
"Select as Best" below if you find the answer a valid solution to your issue.
Hi
I have nevertheless opened a case with docusign.
we have found that the docusign dev environment is not identical to the production environment. as a result, the tests and modifications made in dev were not working in production.
If the user's language differs from the template language, the field doesn't appear, whereas before, when I filled in the API, there was no problem.