Skip to main content
J
James385314232o55
Participating Frequently
July 10, 2024
Question

Sudden CONDITIONAL_PHRASE_TAG length limit

  • July 10, 2024
  • 1 reply
  • 1070 views

Hello,

Today my application is running into this issue with a long conditional phrase. We have not made changes in months to the document or the codebase but this issue seemed to start last night. Have there been changes in regards to this?

 

I am using the Adobe PDF Services SDK and the bad response comes from this line of code:

documentMergeOperation.Execute(object);

 

With a response similar to:

CONDITIONAL_PHRASE_TAG with name "ExampleTextLongerThan400" of length greater than 400 is not allowed.;

 

I am on version 3.4.0 in .NET.

This topic has been closed for replies.

1 reply

Raymond Camden
Community Manager
Raymond CamdenCommunity Manager
Community Manager
July 10, 2024

Can you share the condition from your Word doc? You can rename stuff if it is sensitive, but try to keep it the same length.

J
James385314232o55Author
Participating Frequently
July 10, 2024

Here is my expression: expr(State.AbrreviaState = "CA" or State.AbrreviaState = "CO" or State.AbrreviaState = "CT" or State.AbrreviaState = "FL" or State.AbrreviaState = "IN" or State.AbrreviaState = "IA" or State.AbrreviaState = "KS" or State.AbrreviaState = "LA" or State.AbrreviaState = "ME" or State.AbrreviaState = "MD" or State.AbrreviaState = "MA" or State.AbrreviaState = "MO" or State.AbrreviaState = "NJ" or State.AbrreviaState = "NY" or State.AbrreviaState = "NC" or State.AbrreviaState = "ND" or State.AbrreviaState = "OK" or State.AbrreviaState = "PA" or State.AbrreviaState = "SC" or State.AbrreviaState = "TX" or State.AbrreviaState = "VA" or State.AbrreviaState = "VT" or State.AbrreviaState = "WA" or State.AbrreviaState = "WI" or State.AbrreviaState = "WV" or State.AbrreviaState = "WY")

 

It is definitely over 400 characters and always has been, I am just wondering why now there is validation for it.

Raymond Camden
Community Manager
Raymond CamdenCommunity Manager
Community Manager
July 10, 2024

I raised this internally. For a solution RIGHT now, I suggest that in code, you handle this condition and use a new thing like, okState:true or okState:false. To be fair, I'd recommend that anyway to keep the 'logic' in Word simpler. Again though, this is reported, but I suggest making the change in code for now.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices