Hello,
I’m spinning my wheels. I have created new print sets for processing T1ADJ. I am trying to hide our normal print sets and just show the T1 ADJ print sets, but am struggling with the relevant condition. I am also trying to refrain from using a Custom Field. I already have conditions in some of the print sets so I will need to add the condition to the condition I already have (eg. customfield(“PAPERCOPY”)=“Yes”.)
I thought of using the T1EfileTransmission workflow checkbox. If the return has been efiled, the normal print sets will disappear and the T1ADJ print sets will appear. I can’t get the formatting right for if this box is checked or not checked.
Can someone help me out? I’m open to using another field, but am struggling to figure out what that is or how to do it.
Thanks so much!
How about this field: CurrentClient.Adjustments[-1].T1ADJ.AdjustmentDetails[-1].AmountOfChange
That is the first line on the T1adj form? If so, I think I could use that as well and thought about it. I am also struggling with formatting the entire conditional statement.
For future reference (for others–because it sounds like you know already how to copy a Workflow ID), here’s the help topic that talks about getting the workflow IDs: Workflow IDs - Templates - TaxCycle
(This was the first thing I looked at to help answer your question.)
That said, there is also another page where you can grab EFILE-related field codes:
You would then use one of the following conditions.
These first two will check whether the T1 return was transmitted (T1 EFILE):
CurrentClient.Filing.IsT1Transmitted=True
CurrentClient.Filing.IsT1Transmitted=False
These two will check whether T1-ADJ was transmitted (T1 ReFILE):
CurrentClient.Filing.IsT1RefileTransmitted=True
CurrentClient.Filing.IsT1RefileTransmitted=False
Yes, you could use the workflow items, but I found this was faster and easier for me.
Hope this helps.
That definitely helped. I got the print sets to show or hide like I wanted.
I am running into one other glitch which I’m sure you can help me with. I am trying enter a conditional statement into an email template based on a value in a custom field and I can’t figure out what I have wrong.
This is my condition:
{{# CurrentClient}}{{customfield(“T1ADJAMT”) > 300}} - I’ve also tried quotes around the 300.
I have got this to work:
{{#CurrentClient}}{{# CustomFields.Table[3].CustomMoney > 300}}
The problem with this is it references a position in the table, which may not be the same on every client.
This is my Custom Data.
What do I have wrong in the condition that refers to the Custom Field name?
Thanks again!
Happy to help. Btw, @teresas, you’re doing a great job with figuring out how to write code.
In this case, I believe the problem is that your condition has “curly quotes” instead of straight quotes around the field id. Check out this piece of code to see what I mean:
{{#CurrentClient}}
Testing curly quotes from @teresas: {{customfield(“T1ADJAMT”) > 300}}
Writing from scratch with straight quotes: {{ customfield("T1ADJAMT") > 300 }}
{{# customfield("T1ADJAMT") > 300 }}
Show this when the amount is greater than $300.
{{/ customfield("T1ADJAMT") > 300 }}
{{/CurrentClient}}
To write a condition, I often remove the # from the code to test it. By doing this, it will give me a “true” or “false” response in the preview.
The first thing I did was take your piece of code that wasn’t working, copied it into notepad to clear any formatting, and copied and pasted it into the template editor. This removes any HTML that may be hanging around when I paste it into the template editor. This can often break conditions that look correct.
I could see that your code didn’t work, so I decided to build the condition from scratch by typing it in. When I did that, it used straight quotes and it made the all the difference.
Next, at the bottom, I created the condition again so that I could test whether the sentence would show or hide. And it worked great with the straight quotes. Here’s the screen captures of the final result.
You rock! No wonder I was stumped. I would never have figured that out in a million years!
1 Like
You’re welcome. The Template Editor is quirky that’s for sure.
1 Like
