Does anyone out there know how, (If it's possible) To change the text or backround colours based on a parameter? My exact purpose would be to highlight if a membership was current, expired, about expire, etc. In the header. Thoughts?
Chris
Sure, just select the field you want to vary, go into the Properties area, click the font tab, and look for the "Text color" parameter. Next to it will be a little button that's a blue equals sign with a black slash through it, indicating that you have not set up any rules for it. Click it and you will get a box where you can write a rule.
So if you have an expired flag somewhere, for instance, and you want to make the text red when it's expired, you would write if( expired_flag = 1, RGB(255,0,0), RGB(0,0,0))
There's a color table in the Infomaker built in help system under RGB Infomaker expression function.
Unfortunately Jennifer, that isn’t helping. I absolutely can’t figure out what I’m doing wrong and I’ve been trying to figure it out for almost a week now!!!! Any other suggestions?????
Teresa
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jennifer McClure Sent: Tuesday, June 29, 2010 8:27 AM To: Teresa Dean Subject: Re: [Tessitura Technical Forum] InfoMaker Question
In the report in infomaker, have you checked rows ->sort and made sure the MOS is sorted first? That one used to get me when grouping in infomaker...
From: Teresa Dean <bounce-teresadean9276@tessituranetwork.com> Sent: 6/29/2010 7:34:12 AM
I've been working on trying to modify a custom report for almost a week now and I'm about ready to throw my hands up and give up in defeat. I'm trying to group in InfoMaker and this is a new thing for me. I feel like I understand how it should work, but I'm running into a really frustrating issue. One of my groupings is by MOS but when I run the report, I'm getting "gooesoft_report_parameter.data_column" where the MOS should be. I believe this has something to do do with Report Set up, but I can't figure out what is wrong with it. When I run the SP in SQL, it generates what I would expect the report to be displaying. The MOS displays properly. Has anyone else had this happen and can tell me what I may have done wrong with either InfoMaker or my Report SetUp?
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
I would recommend submitting a help ticket – they have been very good at helping me fix Infomaker errors like this.
Penny Tabor IT Manager Midland Center for the Arts Midland, MI 48640
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Teresa Dean Sent: Tuesday, June 29, 2010 9:37 AM To: Tabor, Penny Subject: RE: [Tessitura Technical Forum] InfoMaker Question
This sounds to me like Tessitura is seeing the wrong version of the datawindow you are working with. When you see junk characters or database column names in a report display it typically means the column specifications don’t match the SQL query or stored procedure result set.
-Ryan
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Teresa Dean Sent: Tuesday, June 29, 2010 9:37 AM To: Ryan Creps Subject: RE: [Tessitura Technical Forum] InfoMaker Question
Thanks Ryan for the info….I’m still stumped though. I just can’t figure out what I have wrong. I’ve just submitted a ticket on TASK so a fresh set of eyes can take a look at it for me.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ryan Creps Sent: Tuesday, June 29, 2010 10:27 AM To: Teresa Dean Subject: RE: [Tessitura Technical Forum] InfoMaker Question
Thanks David…that is exactly what it was (I just couldn’t see it because I had been staring at and working on the report for several days straight and everything was blurring together). Brian Pedaci helped locate the issue after I submitted a help ticket.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Woodall Sent: Tuesday, June 29, 2010 3:39 PM To: Teresa Dean Subject: Re: [Tessitura Technical Forum] InfoMaker Question
Teresa,
One thing to check is that the Column Specifications in Infomaker match the output set of the stored procedure, including field lengths. This can cause all sort of mayhem if they don't match exactly.
David
Anyone know how to make a field wrap/truncate to a second line in an Infomaker report when it runs out of space?
Penny Tabor
IT Manager
Midland Center for the Arts
Midland, MI 48640
Hi Penny, try by checking the “Autosize Height” option in “Position” tab for the particular field.
Mo
Business Analyst
The National Ballet of Canada
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Penny Tabor Sent: Thursday, September 23, 2010 11:22 AM To: Mohiuddin Faruqe Subject: [Tessitura Technical Forum] Infomaker Question
I figured it out – thanks.
Penny
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Penny Tabor Sent: Thursday, September 23, 2010 11:22 AM To: Tabor, Penny Subject: [Tessitura Technical Forum] Infomaker Question
Hi Mo: Good to hear from you again. Yes, that is exactly what I found that worked. Thanks!
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Mohiuddin Faruqe Sent: Thursday, September 23, 2010 12:07 PM To: Tabor, Penny Subject: RE: [Tessitura Technical Forum] Infomaker Question
Hey Harry! Good to hear from you.
Here’s a link to the bible: http://www.tessituranetwork.com/.../Customizations/Custom_Report_Setup.ashx,
I have a customization working on the reprint side, but never could quite get the first round together. Figured it was the data window that drove the first part of the renewal form script -> go get the data, but I could be totally bonkers. This time of year, it’s a coin toss.
As time waits for no one, I’ll have to tinker with it when the print deadline isn’t breathing down my neck.
Dot
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Harry Hoang Sent: Tuesday, February 21, 2017 1:01 PM To: Dot Krebs <dkrebs@actorstheatre.org> Subject: Re: [Tessitura Technical Forum] Infomaker Question
Hello Dot,
We are SFJAZZ about to do some custom report in membership renewal. However, I can't find any documents how to infomaker get connected with Tessitura report system. I know the w_renewal_report is the name of the system window that connects b/w the report in infomaker, where stored procedure needs to define here, and Tess report system. First thing, I'd like to know what to use to open and edit/create a new w_renewal_report for custom any report.
I believe you need to have InfoMaker and report setup utilities are set up on your 2x account if you are having RAMP. You will see the relationship between them.
Regards,
-Harry
From: Dot Krebs <bounce-dotkrebs9366@tessituranetwork.com> Sent: 2/16/2017 4:45:02 PM
Have a question for an InfoMaker mad scientist out there. Yeah, you know who you are.
I noticed that both of the canned Subscription Renewal Notices (all and reprint) open a different InfoMaker Window, but yet, can use the same InfoMaker report to produce the forms.
So, what's up with that?
What is the purpose of w_renewal_report_all and w_renewal_report in InfoMaker?
I'm going to a road where I would need two report formats and I'd kind of like to get away from that if I could by using a Data Window.
Hi, Dot,
Standard reports use a system window called w_report_psr. These windows (w_renewal_report and w_renewal_report_all) are specific to Subscription Renewal Notices in that they handle formats set in T_FORMAT_INFO, but run a specific procedure for generating (or reprinting) renewal notices.
If you start a custom format from the existing sample renewal notice formats, the window runs the standard procedure (TP_GEN_RENEWAL_NOTICES) for generating or reprinting renewal notices. If you start with a brand new datawindow, can start with your own SQL Select or stored procedure. These report windows know to look for this and use it…the caveat being that the standard procedure will not be run. In this case, you have one of two options. One, you can run TP_GET_RENEWAL_NOTICES yourself in a custom procedure (don’t alter the standard proc!). Two, you can run the regular process to a standard format, then use the reprint for a custom format (with the additional data you may need).
Hope this helps
-Ryan Creps
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Dot Krebs Sent: Thursday, February 16, 2017 1:50 PM To: Ryan Creps <rcreps@tessituranetwork.com> Subject: [Tessitura Technical Forum] Infomaker Question
Thanks Ryan.
Yep. That helps a lot.
Thanks,
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ryan Creps Sent: Tuesday, February 21, 2017 7:03 PM To: Dot Krebs <dkrebs@actorstheatre.org> Subject: RE: [Tessitura Technical Forum] Infomaker Question