Is there a report that will pull the notes from the research tab? I'm afraid not, but thought i'd ask!
Thanks!
Brandon
Brandon -
It depends on what you need. If you have a list of people you can run the Full Bio report (found in the Development folder) and select only the notes section.
HTH,
HeatherSeattle Rep
Awesome!! Thanks, Heather! Never would've known that was there..
I have a report that we have scheduled to run weekly for Dev that spits out all Research notes past a given start date. Here’s the query, which can certainly be modified:
CREATE procedure [dbo].[lrp_dev_notes]
( @start_dt datetime
)
as
declare @cust_notes table
( cust_notes_no int,
customer_no int,
esal1_desc varchar(55),
description varchar(30),
created_by char(8),
create_dt datetime,
last_updated_by char(8),
last_update_dt datetime,
notes varchar(255),
serial_order int
insert into @cust_notes
( cust_notes_no,
customer_no,
esal1_desc,
description,
created_by,
create_dt,
last_updated_by,
last_update_dt,
notes,
serial_order
select
a.cust_notes_no,
a.customer_no,
d.esal1_desc,
c.description,
a.created_by,
a.create_dt,
a.last_updated_by,
a.last_update_dt,
b.notes,
b.serial_order
from tx_cust_notes a
join tx_cust_notes_ext b on a.cust_notes_no = b.cust_notes_no
join tr_cust_notes_type c on a.note_type = c.id
join tx_cust_sal d on a.customer_no = d.customer_no and d.signor = 0
where a.create_dt >= @start_dt
or a.last_update_dt >= @start_dt
order by a.cust_notes_no, b.serial_order
select distinct
cust_notes_no,
(select '' + notes from @cust_notes a where a.cust_notes_no = b.cust_notes_no order by customer_no for xml path('')) as notegroup
from @cust_notes b
group by cust_notes_no,
last_update_dt
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Heather Kraft Sent: Thursday, November 19, 2009 6:42 PM To: Lucie Spieler Subject: Re: [Tessitura Technical Forum] Research Notes
Heather Seattle Rep
From: Brandon Walls <bounce-brandonwalls7585@tessituranetwork.com> Sent: 11/19/2009 5:11:19 PM
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 have just been looking at this report for the first time over the past couple of days. For some reason though, neither the Notes nor Subscription History sections are being populated when I run this report, for individual constituents or a list. This happens both when I run the full report and if I just choose those individual sections. All other sections are populating.
Any ideas on where I should look to correct this?
Thanks,
Duane
Same here, Duane. Our in house version of basically the same report works fine, though!
Duane,
For the notes, check TR_CUST_NOTES_TYPE and make sure the "ok to print" box is checked for the note types you want to appear on this report.
Dale
Hi Dale,
That was it, checking the Ok box worked. Thank you!
Now, I just need to solve the Subscription History issue.
Huh...I didn't realize sub history wasn't working either.Looks like the d_biography_new .pbl calls d_bio_subscription_newwhich populates data based upon the view LV_SUB_HIST_REPORT.I don't know about you all but it doesn't look like my view was ever changed to point towards my custom history tables/views.I assume since this is a local view we are welcome to update it.
Cheers!
--edited out dddw since I don't think that was an accurate term.
Yes, LV_SUB_HIST_REPORT is available to sites for customization, within the restriction that the columns returned must match the dataset expected in the standard datawindow.
You can also override the subscription section with a local datawindow as well using a datawindow of the same name (d_bio_subscription_new) in a library referenced in LOCAL_PRE_LIBRARY_LIST (T_DEFAULTS). Doing this allows you to use whatever method and columns that you wish.
-Ryan
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ryan Rowell Sent: Monday, November 23, 2009 3:47 PM To: Ryan Creps Subject: Re: [Tessitura Technical Forum] Research Notes
Huh...I didn't realize sub history wasn't working either. Looks like the b_biography_new .pbl calls the dddw b_bio_subscription_new which populates data based upon the view LV_SUB_HIST_REPORT. I don't know about you all but it doesn't look like my view was ever changed to point towards my custom history tables/views. I assume since this is a local view we are welcome to update it.
From: Duane Woods <bounce-duanewoods8158@tessituranetwork.com> Sent: 11/23/2009 2:16:33 PM