Behavior of Export Criteria changed?
We have Solicitors with start and end dates (Date From and Date To on the Relationship record). Historically we’ve had several different Solicitor Types, but currently only use a “Primary Solicitor” and when that Solicitor is no longer assigned they get a Date To and the new Primary Solicitor is assigned with a Date From. I’m trying to get the current Primary Solicitor out of the system, but no matter what I do I keep getting the wrong person who left our org more than a year ago.
I’ve just run a series of tests trying to export a single “Primary Solicitor” using a Constituent Export. To make the test quick and easy I’m exporting one specific Constituent record to Excel and only exporting Relationships -> Assigned Solicitors -> Name. I’ve tried “Order by” Date From, Date To, System Record ID, Name, even Sort Name. I’ve tried both Ascending and Descending with each of those options. NOTHING changes the result.
If I export 2 or more records I can get the active Solicitor, but that isn’t useful for the required end result because I need easy reporting of that one Primary Solicitor. If I export 2 records the name sort does work (Ascending and Descending), so it seems that RE is performing the record count limit first, then performing the sort.
If I put today’s date in the Start Date field I can get good results, but I need the production version of this Export to run without having to be altered (it’s used for a Custom Report and end users need to be able to easily run the report without having to go into the Export setup every time).
I’m certain I used to get the desired result (sort performed then the record limit applied) in 7.93 (unfortunately I don’t have access to 7.93 to run tests anymore). It’s looking like I’ll have to export all Solicitors with their to/from dates and filter down to the right person using a subreport in Crystal Reports. GRRR!
Comments
-
John Heizer:
It seems that somewhere between RE 7.93 and RE 7.96 Patch 8 they have changed the behavior of Criteria for exporting Assigned Solicitors (probably for all Relationships).
We have Solicitors with start and end dates (Date From and Date To on the Relationship record). Historically we’ve had several different Solicitor Types, but currently only use a “Primary Solicitor” and when that Solicitor is no longer assigned they get a Date To and the new Primary Solicitor is assigned with a Date From. I’m trying to get the current Primary Solicitor out of the system, but no matter what I do I keep getting the wrong person who left our org more than a year ago.
I’ve just run a series of tests trying to export a single “Primary Solicitor” using a Constituent Export. To make the test quick and easy I’m exporting one specific Constituent record to Excel and only exporting Relationships -> Assigned Solicitors -> Name. I’ve tried “Order by” Date From, Date To, System Record ID, Name, even Sort Name. I’ve tried both Ascending and Descending with each of those options. NOTHING changes the result.
If I export 2 or more records I can get the active Solicitor, but that isn’t useful for the required end result because I need easy reporting of that one Primary Solicitor. If I export 2 records the name sort does work (Ascending and Descending), so it seems that RE is performing the record count limit first, then performing the sort.
If I put today’s date in the Start Date field I can get good results, but I need the production version of this Export to run without having to be altered (it’s used for a Custom Report and end users need to be able to easily run the report without having to go into the Export setup every time).
I’m certain I used to get the desired result (sort performed then the record limit applied) in 7.93 (unfortunately I don’t have access to 7.93 to run tests anymore). It’s looking like I’ll have to export all Solicitors with their to/from dates and filter down to the right person using a subreport in Crystal Reports. GRRR!
I've had this problem from the start. I use relationships to assign coaches to their funds. I do exactly what you did with exporting two and then I delete one. But I'm going into Excel so that's not an issue. What is the point of having a "To" date if it means nothing? RE's logic isn't always common sense. Unfortunately, you may have to change them all to "Former" and only leave the current one as "Primary".
2 -
I was told a long time ago by support that the "order by" only works if you export more than one record. This applies to other fields also, not just solicitor.
We change any former solicitors to "Former Primary Solicitor" to avoid this problem.4 -
Hi John-
If I put today’s date in the Start Date field I can get good results, but I need the production version of this Export to run without having to be altered (it’s used for a Custom Report and end users need to be able to easily run the report without having to go into the Export setup every time).
Unfortunately, this isn't new and it's for this precise reason I stopped allowing constituent records to have multiple Constituent Codes using the Date Froms and Date Tos to manage them. It's also why I stopped assigning multiple solicitors of the same Solicitor Type using Date Froms and Date Tos to manage those relationships. You have to populate the Date From in Export, as you've discovered, to get the correct results and you have to change it every day you run it.
Let's assume for a moment that my constituent record has the Constituent Code Student with a Date From of 1/1/17 and a Date To of 12/31/17. Let's also assume I have second Constituent Code of Alumni with a Date From of 1/1/18. If I export both the Alumni and Student Constituent Codes and I do NOT populate the Date From field with today's date, I will see both Constituent Codes come out in Export. Nice, eh?
My current practice is to only allow each constituent to have one Constituent Code (I track past codes via Relationships to Orgs). This precludes the need of updating the Date From field each and every time I run my Export. Same thing for Assigned Solicitors, I change the Solicitor Type from Primary to Former so again, I don't need to update the Date From fields to get the correct data.
Raiser's Edge quirks are fun, aren't they?0 -
Marie Stark:
I was told a long time ago by support that the "order by" only works if you export more than one record. This applies to other fields also, not just solicitor.Even then, I think the sorting is done after the selection so you're still not guaranteed to get the results you're after, unless you export enough columns to cover the maximum number of solicitors any constituent has.
0 -
Incidentally the one place where this doesn't cause as much of a problem is phones. Raiser's Edge physically displays primary phones at the top of the list on the constituent record, and in my experience always exports these first, so you can safely export just one phone number and know that it's going to be the primary. If the constituent has a primary phone. If they don't have a phone marked as primary, unfortunately all bets are off and RE is just going to give you whichever one it comes to first, as per the solicitors etc.
Quite why RE is capable of performing this primary phone sort prior to selection but not others, I have no idea...2 -
Alan French:
Incidentally the one place where this doesn't cause as much of a problem is phones. Raiser's Edge physically displays primary phones at the top of the list on the constituent record, and in my experience always exports these first, so you can safely export just one phone number and know that it's going to be the primary. If the constituent has a primary phone. If they don't have a phone marked as primary, unfortunately all bets are off and RE is just going to give you whichever one it comes to first, as per the solicitors etc.
Quite why RE is capable of performing this primary phone sort prior to selection but not others, I have no idea...Here's my theory: pretty much every record in every table in RE has a "sequence" column, which establishes the sequence in which it will consider the records. For some things you can change this sequence -- when you move an address to the top in the addresses tab, or a constituent code up to the top line, or a membership up to the top in the addresses tab, it changes the sequence field to 1 in that record. That's why if you export one constituent code, you get the primary one, or one phone, it'll give you the primary -- it's looking for the lowest sequence field.
But relationships don't work that way -- despite there being a sequence field, there isn't a way to change it on the relationships or solicitors from the front end of RE. So when you export one solicitor, RE acts the same way it does for other things and pulls the lowest sequence it finds. As we found above, for constituent codes or addresses, it's going to be the primary one because it's changed the sequence field to 1. But for solicitors, it's probably going to be the oldest one you entered, because there's no way to change it.
I could be wrong! I haven't seen the code behind the export function and my access to the back end of RE is read-only, so I can't test it. But that's my working theory. Alan, if you have back end access you can write a little query on the table CONSTIT_SOLICITORS to find that record's solicitors and see if the one that pulls incorrectly is indeed the lowest sequence for your Primary Solicitors on that record.
1 -
John Heizer:
It seems that somewhere between RE 7.93 and RE 7.96 Patch 8 they have changed the behavior of Criteria for exporting Assigned Solicitors (probably for all Relationships).
We have Solicitors with start and end dates (Date From and Date To on the Relationship record). Historically we’ve had several different Solicitor Types, but currently only use a “Primary Solicitor” and when that Solicitor is no longer assigned they get a Date To and the new Primary Solicitor is assigned with a Date From. I’m trying to get the current Primary Solicitor out of the system, but no matter what I do I keep getting the wrong person who left our org more than a year ago.
I’ve just run a series of tests trying to export a single “Primary Solicitor” using a Constituent Export. To make the test quick and easy I’m exporting one specific Constituent record to Excel and only exporting Relationships -> Assigned Solicitors -> Name. I’ve tried “Order by” Date From, Date To, System Record ID, Name, even Sort Name. I’ve tried both Ascending and Descending with each of those options. NOTHING changes the result.
If I export 2 or more records I can get the active Solicitor, but that isn’t useful for the required end result because I need easy reporting of that one Primary Solicitor. If I export 2 records the name sort does work (Ascending and Descending), so it seems that RE is performing the record count limit first, then performing the sort.
If I put today’s date in the Start Date field I can get good results, but I need the production version of this Export to run without having to be altered (it’s used for a Custom Report and end users need to be able to easily run the report without having to go into the Export setup every time).
I’m certain I used to get the desired result (sort performed then the record limit applied) in 7.93 (unfortunately I don’t have access to 7.93 to run tests anymore). It’s looking like I’ll have to export all Solicitors with their to/from dates and filter down to the right person using a subreport in Crystal Reports. GRRR!
John, I'm moving quickly this evening and I see others have posted, but perhaps this will help...sorry if it duplicates information already shared...
From my notes of 8/29/11 about a similar issue with a client:
I found out (Blackbaud KB BB602606) that if only one of an item is exported the Order by doesn’t work. J So I changed the export to export two email addresses. The merges should work better now—the right email address should be in the first email fields which we have mapped to the email process, and the second email address fields can just be ignored. Keep an eye out, but I don’t see any reason why things shouldn’t be fine.
I tested specifically on John Smith and saw that the export as is did bring out b and not a. When I simply said to export two instead of one, a showed up first.Solution ID: Product: Published: Updated: Description
When exporting specific fields such as assigned solicitors, contacts, or other fields, you can indicate how many and which ones you want to export. When indicating multiple options you can select an 'Order by' field to select the order you want to select fields for the export. For example if you are exporting contacts and a record has multiple contacts, you can indicate you want contact A found and exported first. The "order by" field appears to ignore its settings if we are only exporting one contact, assigned solicitor, or other fields.Answer
Alternate solution:
When double clicking on the field to export, you will be prompted, "for each constituent, enter the number of (selected field) to export". A number greater than 1 must populate this field for the "order by" sorting to work.
Once the file has exported, user can simply proceed to delete the secondary column that will appear in the file.
0 -
John Heizer:
It seems that somewhere between RE 7.93 and RE 7.96 Patch 8 they have changed the behavior of Criteria for exporting Assigned Solicitors (probably for all Relationships).
We have Solicitors with start and end dates (Date From and Date To on the Relationship record). Historically we’ve had several different Solicitor Types, but currently only use a “Primary Solicitor” and when that Solicitor is no longer assigned they get a Date To and the new Primary Solicitor is assigned with a Date From. I’m trying to get the current Primary Solicitor out of the system, but no matter what I do I keep getting the wrong person who left our org more than a year ago.
I’ve just run a series of tests trying to export a single “Primary Solicitor” using a Constituent Export. To make the test quick and easy I’m exporting one specific Constituent record to Excel and only exporting Relationships -> Assigned Solicitors -> Name. I’ve tried “Order by” Date From, Date To, System Record ID, Name, even Sort Name. I’ve tried both Ascending and Descending with each of those options. NOTHING changes the result.
If I export 2 or more records I can get the active Solicitor, but that isn’t useful for the required end result because I need easy reporting of that one Primary Solicitor. If I export 2 records the name sort does work (Ascending and Descending), so it seems that RE is performing the record count limit first, then performing the sort.
If I put today’s date in the Start Date field I can get good results, but I need the production version of this Export to run without having to be altered (it’s used for a Custom Report and end users need to be able to easily run the report without having to go into the Export setup every time).
I’m certain I used to get the desired result (sort performed then the record limit applied) in 7.93 (unfortunately I don’t have access to 7.93 to run tests anymore). It’s looking like I’ll have to export all Solicitors with their to/from dates and filter down to the right person using a subreport in Crystal Reports. GRRR!
I use direct SQL to handle this particular problem. Of course that, in turn gives me the other problem of having to link together information pulled from an in-system query or export with information pulled directly using SQL. All things being equal though, I prefer this to the other alternatives.
Some years ago, "active Primary Solicitor" became a standard field on all our mailing lists-- meaning the below SQL code or a close variation of it has been run a zillion or so times-- meaning I'm reasonably sure it's bug free. You would need to replace all references to "re7_db" to whatever the internal name of your Raiser's Edge database is. Other than that, it should work as written. The actual start end and end dates would need additional processing if you were going to do anything with them as they come through as raw fuzzy dates.
-- Query to pull a list of Constituents' active Primary Solicitor relationshipsSELECT r.CONSTITUENT_ID AS ConstID, r.ID AS SysRecID, cs.ID AS SolRelRecID, cs.IMPORT_ID AS SolRelImpID, SolRec.ID AS SolRecID,
SolRec.IMPORT_ID AS SolRecImpID,
(SELECT SOLICITOR_INACTIVE
FROM re7_db.dbo.RECORDS AS r_i
WHERE (ID = SolRec.ID)) AS SolInactive, CAST(re7_db.dbo.GetSalutation(NULL, SolRec.ID, '', 4, - 4, - 4, NULL) AS varchar(250)) AS SolName,
solType.LONGDESCRIPTION AS SolType, cs.DATE_FROM AS DateFrom, cs.DATE_TO AS DateTo
FROM re7_db.dbo.RECORDS AS r INNER JOIN
re7_db.dbo.CONSTIT_SOLICITORS AS cs ON r.ID = cs.CONSTIT_ID INNER JOIN
re7_db.dbo.TABLEENTRIES AS solType ON cs.SOLICITOR_TYPE = solType.TABLEENTRIESID INNER JOIN
re7_db.dbo.RECORDS AS SolRec ON cs.SOLICITOR_ID = SolRec.ID
WHERE (cs.DATE_TO IS NULL) AND (cs.DATE_FROM IS NULL) AND (solType.LONGDESCRIPTION = 'Primary Solicitor') OR
(cs.DATE_FROM IS NULL) AND (solType.LONGDESCRIPTION = 'Primary Solicitor') AND (re7_db.dbo.Format_FuzzyDateForRange(cs.DATE_TO, 0)
>= re7_db.dbo.FuzzyDate(GETDATE())) OR
(cs.DATE_TO IS NULL) AND (solType.LONGDESCRIPTION = 'Primary Solicitor') AND (re7_db.dbo.Format_FuzzyDateForRange(cs.DATE_FROM, - 1)
<= re7_db.dbo.FuzzyDate(GETDATE())) OR
(solType.LONGDESCRIPTION = 'Primary Solicitor') AND (re7_db.dbo.Format_FuzzyDateForRange(cs.DATE_TO, 0) >= re7_db.dbo.FuzzyDate(GETDATE())) AND
(re7_db.dbo.Format_FuzzyDateForRange(cs.DATE_FROM, - 1) <= re7_db.dbo.FuzzyDate(GETDATE()))
2 -
What a week (or rather, two) to have to ignore the Community! I just had this same issue when trying to export the most recent Action for a list of records. Fortunately, I'm able to export 2 fields and then delete one in Excel after the export. But frustrating. And it makes me wonder if I've ever inadvertently gotten incorrect data from an Export because of this. I don't recall there being any disclaimer on the window where you set the order. (I also wish you could set the order to something other than Ascending or Descending, but that's another issue.)
Someone, I now forget who, said something about moving an Address to the top of the list...how does one do that? I've often wanted to, but couldn't ever figure out how to reorder Addresses.0 -
Jen Claudy:
Someone, I now forget who, said something about moving an Address to the top of the list...how does one do that? I've often wanted to, but couldn't ever figure out how to reorder Addresses.There are little up and down arrows right above the addresses, to the right of the filter combo box.
0 -
I have NEVER noticed those, thanks!
I think this is one of those cases where a lack of consistency makes RE less intuitive than it could be. One screen will have buttons that say "up" and "down" whereas another will have arrows; fields have different names in Query than they do in Export etc.1 -
Alan French:
I have NEVER noticed those, thanks!
I think this is one of those cases where a lack of consistency makes RE less intuitive than it could be. One screen will have buttons that say "up" and "down" whereas another will have arrows; fields have different names in Query than they do in Export etc.WOW! I'd never noticed them either. I'm assuming that this is what's being used in address processing as "First address found."
0 -
John Heizer:
Alan French:
I have NEVER noticed those, thanks!
I think this is one of those cases where a lack of consistency makes RE less intuitive than it could be. One screen will have buttons that say "up" and "down" whereas another will have arrows; fields have different names in Query than they do in Export etc.WOW! I'd never noticed them either. I'm assuming that this is what's being used in address processing as "First address found."
Exactly! And when you move it, it changes that sequence field, and that's what it looks for to define 'first address found.'
At least, like I said, that's my theory. I could be wrong.
0 -
James Andrews:
Jen Claudy:
Someone, I now forget who, said something about moving an Address to the top of the list...how does one do that? I've often wanted to, but couldn't ever figure out how to reorder Addresses.There are little up and down arrows right above the addresses, to the right of the filter combo box.Oops...I thought you meant reorder/sort on the [Addresses] Tab of a Constituent Record.
0 -
Yes you were right Jen, it is on the Address tab on the constituent record. I think the screenshot from Quick Letters was only to illustrate the "first address found" option - just an unfortunate coincidence that there's also a set of up and down arrows on that screen!0
-
I wish I would have read this sooner. I come off a query where I have sorted out "date to equals blank" to get my current assigned solicitors. Sometimes I also export all of the assigned solicitors (excel) and by including date from and date to columns, I'm able to quickly spot the currently solicitors.
John Heizer:
It seems that somewhere between RE 7.93 and RE 7.96 Patch 8 they have changed the behavior of Criteria for exporting Assigned Solicitors (probably for all Relationships).
We have Solicitors with start and end dates (Date From and Date To on the Relationship record). Historically we’ve had several different Solicitor Types, but currently only use a “Primary Solicitor” and when that Solicitor is no longer assigned they get a Date To and the new Primary Solicitor is assigned with a Date From. I’m trying to get the current Primary Solicitor out of the system, but no matter what I do I keep getting the wrong person who left our org more than a year ago.
I’ve just run a series of tests trying to export a single “Primary Solicitor” using a Constituent Export. To make the test quick and easy I’m exporting one specific Constituent record to Excel and only exporting Relationships -> Assigned Solicitors -> Name. I’ve tried “Order by” Date From, Date To, System Record ID, Name, even Sort Name. I’ve tried both Ascending and Descending with each of those options. NOTHING changes the result.
If I export 2 or more records I can get the active Solicitor, but that isn’t useful for the required end result because I need easy reporting of that one Primary Solicitor. If I export 2 records the name sort does work (Ascending and Descending), so it seems that RE is performing the record count limit first, then performing the sort.
If I put today’s date in the Start Date field I can get good results, but I need the production version of this Export to run without having to be altered (it’s used for a Custom Report and end users need to be able to easily run the report without having to go into the Export setup every time).
I’m certain I used to get the desired result (sort performed then the record limit applied) in 7.93 (unfortunately I don’t have access to 7.93 to run tests anymore). It’s looking like I’ll have to export all Solicitors with their to/from dates and filter down to the right person using a subreport in Crystal Reports. GRRR!
0 -
John Heizer:
It seems that somewhere between RE 7.93 and RE 7.96 Patch 8 they have changed the behavior of Criteria for exporting Assigned Solicitors (probably for all Relationships).
We have Solicitors with start and end dates (Date From and Date To on the Relationship record). Historically we’ve had several different Solicitor Types, but currently only use a “Primary Solicitor” and when that Solicitor is no longer assigned they get a Date To and the new Primary Solicitor is assigned with a Date From. I’m trying to get the current Primary Solicitor out of the system, but no matter what I do I keep getting the wrong person who left our org more than a year ago.
I’ve just run a series of tests trying to export a single “Primary Solicitor” using a Constituent Export. To make the test quick and easy I’m exporting one specific Constituent record to Excel and only exporting Relationships -> Assigned Solicitors -> Name. I’ve tried “Order by” Date From, Date To, System Record ID, Name, even Sort Name. I’ve tried both Ascending and Descending with each of those options. NOTHING changes the result.
If I export 2 or more records I can get the active Solicitor, but that isn’t useful for the required end result because I need easy reporting of that one Primary Solicitor. If I export 2 records the name sort does work (Ascending and Descending), so it seems that RE is performing the record count limit first, then performing the sort.
If I put today’s date in the Start Date field I can get good results, but I need the production version of this Export to run without having to be altered (it’s used for a Custom Report and end users need to be able to easily run the report without having to go into the Export setup every time).
I’m certain I used to get the desired result (sort performed then the record limit applied) in 7.93 (unfortunately I don’t have access to 7.93 to run tests anymore). It’s looking like I’ll have to export all Solicitors with their to/from dates and filter down to the right person using a subreport in Crystal Reports. GRRR!
As at least one other person mentioned, the sort "feature" in Export only works if you export more than one of whatever it is. BUT, it works and does work with as little as 2 of each solicitor, relationship or whatever. Good luck!
0 -
John, I have a daily gift report that is a combination of a Constituent and a gift export and I have had this issue off and on. I am currently pulling the assigned solicitor selecting two and sorting by date from Descending. It seems to be working right now. I checked suppress duplicated and that seems to help in only pulling one value. I am curious to hear how you would use it in a subreport to avoid this issue. And like others I have also contemplated using a former so that there is only one active solicitor at a time.0
-
Snigdha Verma:
John, I have a daily gift report that is a combination of a Constituent and a gift export and I have had this issue off and on. I am currently pulling the assigned solicitor selecting two and sorting by date from Descending. It seems to be working right now. I checked suppress duplicated and that seems to help in only pulling one value. I am curious to hear how you would use it in a subreport to avoid this issue. And like others I have also contemplated using a former so that there is only one active solicitor at a time.I've used a hidden subreport to look at all assigned Solicitors, determine which one is the current primary, and pass that value back up to the main report.
0 -
John, I ran into that a few months back working in a database recently converted to RE. What we resolved to do was to only use the designation "Primary Solicitor" for the currently active solicitor - the one with a Date From and no Date To yet. For the previous staff solicitors, they all had Date From and To ranges, so we simply removed the solicitor Type and we preserved the history of the existence of the relationship. Alternatively, you could change the Solicitor Type to "Former staff solicitor" or "Former Primary Solicitor" - whatever works so that each assigned donor only EVER has one Solicitor Relationship designated as "Primary." It was an easy fix!
1 -
J Baumann:
John, I ran into that a few months back working in a database recently converted to RE. What we resolved to do was to only use the designation "Primary Solicitor" for the currently active solicitor - the one with a Date From and no Date To yet. For the previous staff solicitors, they all had Date From and To ranges, so we simply removed the solicitor Type and we preserved the history of the existence of the relationship. Alternatively, you could change the Solicitor Type to "Former staff solicitor" or "Former Primary Solicitor" - whatever works so that each assigned donor only EVER has one Solicitor Relationship designated as "Primary." It was an easy fix!
We have had multiple Solicitor types, not just Primary, and I don't want to clutter things by having multiple "former" types when start and end dates SHOULD be adequate. It's a custom report, so I'm fixing it "the hard way" by creating a hidden subreport that properly processes all Solicitor records and returns only the one that I want. I'm doing the same thing with Constituent Codes, which I'm finding are also not working the same as they did in 7.93 and will allow me to correctly report on what a code was on a prior date when a donor has multiple possibilities.
1 -
John,
I was told at one point to put today's date in the date from field. It makes absolutely no sense really but it does only pull those that are current solicitors and not those with end dates.
Diana Hunt0 -
Hi Diane-
The output makes sense when you populate the date field, in that Export compares the solicitor From Dates and To Dates against the date you entered to determine if someone is an active solicitor, that is to say, the solicitor's Date To is after the date you entered or blank and the Date From is before the date you entered.
What does not make sense is that Blackbaud would make us take this manual step rather than auto-populating the field for us or even better, take the feature away from us entirely and tell Export to assume the date we want populated in that field is today's date. I guess the thinking was, "What if a user wants to run Export using dates in the future or past to see what the results would be or would have been?" Not a very compelling case if that was the logic, but, there you have it.1 -
Yes, I guess that does make sense. John Heizer, I hope this helps. I use it every time I need current solicitors only.
0 -
Diana Hunt:
Yes, I guess that does make sense. John Heizer, I hope this helps. I use it every time I need current solicitors only.
Thanks Diana, but going back to my original post/issue, I need this to work for a custom report without the person running the report having to open the Export and change the date every time they want to run the report.
0 -
Did anyone discover a solution for the solicitor issue? We use 5 solicitor types. I have had an export which worked flawlessly for the past several years, allowing me to export a column for each type and populate with the current one by putting from date as today and leaving end blank. This is a major step backwards for us as pulling the same report will likely take multiple steps now.
Thanks!0 -
Tracy Ricketts putting in a Start Date of today in the Export criteria should work for you. I was trying to get it to work without having to modify the Export.0
-
Thanks John, but I tried it repeatedly over the last few days and it hasn't worked, which is what drove me to site to search for a solution.0
-
Tracy Ricketts:
Thanks John, but I tried it repeatedly over the last few days and it hasn't worked, which is what drove me to site to search for a solution.I just saw in the Facebook RE User Group that Melissa Graves is having a similar problem exporting Constituent Codes using the Start Date (some records that should pull information are coming up blank). There may have been a bug introduced recently.
1 -
Tracy Ricketts:
Thanks John, but I tried it repeatedly over the last few days and it hasn't worked, which is what drove me to site to search for a solution.Tracey - I am going to have BB connect you to my case. They are collecting names of users where this has just recently changed. Mine is a constituent code issue but at least one other (maybe they are already counting you if you have an open case about it) is having this issue with exporting solicitors.
3
Categories
- All Categories
- Shannon parent
- shannon 2
- shannon 1
- 21 Advocacy DC Users Group
- 14 BBCRM PAG Discussions
- 89 High Education Program Advisory Group (HE PAG)
- 28 Luminate CRM DC Users Group
- 8 DC Luminate CRM Users Group
- Luminate PAG
- 5.9K Blackbaud Altru®
- 58 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 409 bbcon®
- 2.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- donorCentrics®
- 1.1K Blackbaud eTapestry®
- 2.8K Blackbaud Financial Edge NXT®
- 1.1K Blackbaud Grantmaking™
- 527 Education Management Solutions for Higher Education
- 1 JustGiving® from Blackbaud®
- 4.6K Education Management Solutions for K-12 Schools
- Blackbaud Luminate Online & Blackbaud TeamRaiser
- 16.4K Blackbaud Raiser's Edge NXT®
- 4.1K SKY Developer
- 547 ResearchPoint™
- 151 Blackbaud Tuition Management™
- 1 YourCause® from Blackbaud®
- 61 everydayhero
- 3 Campaign Ideas
- 58 General Discussion
- 115 Blackbaud ID
- 87 K-12 Blackbaud ID
- 6 Admin Console
- 949 Organizational Best Practices
- 353 The Tap (Just for Fun)
- 235 Blackbaud Community Feedback Forum
- 55 Admissions Event Management EAP
- 18 MobilePay Terminal + BBID Canada EAP
- 36 EAP for New Email Campaigns Experience in Blackbaud Luminate Online®
- 109 EAP for 360 Student Profile in Blackbaud Student Information System
- 41 EAP for Assessment Builder in Blackbaud Learning Management System™
- 9 Technical Preview for SKY API for Blackbaud CRM™ and Blackbaud Altru®
- 55 Community Advisory Group
- 46 Blackbaud Community Ideas
- 26 Blackbaud Community Challenges
- 7 Security Testing Forum
- 1.1K ARCHIVED FORUMS | Inactive and/or Completed EAPs
- 3 Blackbaud Staff Discussions
- 7.7K ARCHIVED FORUM CATEGORY [ID 304]
- 1 Blackbaud Partners Discussions
- 1 Blackbaud Giving Search™
- 35 EAP Student Assignment Details and Assignment Center
- 39 EAP Core - Roles and Tasks
- 59 Blackbaud Community All-Stars Discussions
- 20 Blackbaud Raiser's Edge NXT® Online Giving EAP
- Diocesan Blackbaud Raiser’s Edge NXT® User’s Group
- 2 Blackbaud Consultant’s Community
- 43 End of Term Grade Entry EAP
- 92 EAP for Query in Blackbaud Raiser's Edge NXT®
- 38 Standard Reports for Blackbaud Raiser's Edge NXT® EAP
- 12 Payments Assistant for Blackbaud Financial Edge NXT® EAP
- 6 Ask an All Star (Austen Brown)
- 8 Ask an All-Star Alex Wong (Blackbaud Raiser's Edge NXT®)
- 1 Ask an All-Star Alex Wong (Blackbaud Financial Edge NXT®)
- 6 Ask an All-Star (Christine Robertson)
- 21 Ask an Expert (Anthony Gallo)
- Blackbaud Francophone Group
- 22 Ask an Expert (David Springer)
- 4 Raiser's Edge NXT PowerUp Challenge #1 (Query)
- 6 Ask an All-Star Sunshine Reinken Watson and Carlene Johnson
- 4 Raiser's Edge NXT PowerUp Challenge: Events
- 14 Ask an All-Star (Elizabeth Johnson)
- 7 Ask an Expert (Stephen Churchill)
- 2025 ARCHIVED FORUM POSTS
- 322 ARCHIVED | Financial Edge® Tips and Tricks
- 164 ARCHIVED | Raiser's Edge® Blog
- 300 ARCHIVED | Raiser's Edge® Blog
- 441 ARCHIVED | Blackbaud Altru® Tips and Tricks
- 66 ARCHIVED | Blackbaud NetCommunity™ Blog
- 211 ARCHIVED | Blackbaud Target Analytics® Tips and Tricks
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- Luminate CRM DC Users Group
- 225 ARCHIVED | Blackbaud eTapestry® Tips and Tricks
- 1 Blackbaud eTapestry® Know How Blog
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)
- 1 Blackbaud K-12 Education Solutions™ Blog
- 280 ARCHIVED | Mixed Community Announcements
- 3 ARCHIVED | Blackbaud Corporations™ & Blackbaud Foundations™ Hosting Status
- 1 npEngage
- 24 ARCHIVED | K-12 Announcements
- 15 ARCHIVED | FIMS Host*Net Hosting Status
- 23 ARCHIVED | Blackbaud Outcomes & Online Applications (IGAM) Hosting Status
- 22 ARCHIVED | Blackbaud DonorCentral Hosting Status
- 14 ARCHIVED | Blackbaud Grantmaking™ UK Hosting Status
- 117 ARCHIVED | Blackbaud CRM™ and Blackbaud Internet Solutions™ Announcements
- 50 Blackbaud NetCommunity™ Blog
- 169 ARCHIVED | Blackbaud Grantmaking™ Tips and Tricks
- Advocacy DC Users Group
- 718 Community News
- Blackbaud Altru® Hosting Status
- 104 ARCHIVED | Member Spotlight
- 145 ARCHIVED | Hosting Blog
- 149 JustGiving® from Blackbaud® Blog
- 97 ARCHIVED | bbcon® Blogs
- 19 ARCHIVED | Blackbaud Luminate CRM™ Announcements
- 161 Luminate Advocacy News
- 187 Organizational Best Practices Blog
- 67 everydayhero Blog
- 52 Blackbaud SKY® Reporting Announcements
- 17 ARCHIVED | Blackbaud SKY® Reporting for K-12 Announcements
- 3 Luminate Online Product Advisory Group (LO PAG)
- 81 ARCHIVED | JustGiving® from Blackbaud® Tips and Tricks
- 1 ARCHIVED | K-12 Conference Blog
- Blackbaud Church Management™ Announcements
- ARCHIVED | Blackbaud Award Management™ and Blackbaud Stewardship Management™ Announcements
- 1 Blackbaud Peer-to-Peer Fundraising™, Powered by JustGiving® Blogs
- 39 Tips, Tricks, and Timesavers!
- 56 Blackbaud Church Management™ Resources
- 154 Blackbaud Church Management™ Announcements
- 1 ARCHIVED | Blackbaud Church Management™ Tips and Tricks
- 11 ARCHIVED | Blackbaud Higher Education Solutions™ Announcements
- 7 ARCHIVED | Blackbaud Guided Fundraising™ Blog
- 2 Blackbaud Fundraiser Performance Management™ Blog
- 9 Foundations Events and Content
- 14 ARCHIVED | Blog Posts
- 2 ARCHIVED | Blackbaud FIMS™ Announcement and Tips
- 59 Blackbaud Partner Announcements
- 10 ARCHIVED | Blackbaud Impact Edge™ EAP Blogs
- 1 Community Help Blogs
- Diocesan Blackbaud Raiser’s Edge NXT® Users' Group
- Blackbaud Consultant’s Community
- Blackbaud Francophone Group
- 1 BLOG ARCHIVE CATEGORY
- Blackbaud Community™ Discussions
- 8.3K Blackbaud Luminate Online® & Blackbaud TeamRaiser® Discussions
- 5.7K Jobs Board