What does your organization use for exporting proposals?

Options
We would like to have our proposal in rows and not columns. Like a gift query, a long list of gifts...


I built a relationship query which does that but has lots of duplicates and I don’t want to go to excel if I don’t have to. I don’t see an export that links to relationships, does anyone have a suggestion?



Thank you,


Jason 


 

Comments

  • Not for proposals, but I had a similar issue with phone numbers as I often want those in the same sort of layout, in one long column, but need to use export because I can't get the import IDs from a query. I created a custom report that uses an export with the MDB format, then I can export the results from Crystal to Excel.
  • I'm not sure how a Relationship Query connects to Proposals.


    Because Proposals don't have their own "top level" in RE (no such thing as a Proposal Query or Export) it is essentially impossible to report on them accurately without using advanced external tools like Excel or Crystal Reports.  If you're trying to report on Proposals that have a Status of, for example, "Active" then you have to Query for all Constituents that have any Proposal with that Status, export all Proposals from all of those Constituents, then filter down to only the "Active" Proposals outside of RE.
  • Yeah what John said. Export them all and use Access to query for the ones you want. Yes, it takes a long time and is a pain, but there's really no other way to do it without back-end access to the database (which, if you have, is very easy to do).
  • Don't know enough of how Proposals behave in Query, but because somebody mentioned Access-  maybe  you can use Pivot reports (under Reports) instead.  Then you would not have to recreate the filter every time and run it directly out of RE.
  • Our Systems Team built a report in SharePoint for me. Basically, it's kind of a mini-data warehouse that I can access through Excel via SharePoint. It has all the fields found on the General tab of a Proposal plus a few of the "hidden" properties (e.g.) Proposal ID; etc. It displays one-line per Proposal Solicitor, which makes reporting for a particular solicitor, or group of solicitors easy without worrying about duplicates (can use the Excel "Remove Duplicates" if you want all unique Proposals). It doesn't include much constituent data though, so if you need that, you have to copy/paste/merge it with another Export.


    Lauren
  • Would you (Lauren Burgess) be able to send us how your team build the data warehouse for you? That might be a solution for us, because as of now, we are having some trouble getting reporting of solicitors. 


    The data points we really need are: Solicitor, constituent ID, proposal status, last action, last action type and the dates associated with those status.  

    The goal is to manage solicitor activity.


    Thank you all. 
  • I use a constituent query to manage our donor pipeline (proposals).  I've adding naming conventions to the proposal so that we can select only the proposals we want in the query.  The proposal names either begin with 'Pending [Major/Annual/Planned]: Donor Last Name' or with 'YEAR Completed [Major/Annual/Planned]: Donor Last Name'.  This lets me select exactly the data we want by using 'Proposal Name begins with' in the query and output the data with one row for each proposal. 


    I then export directly from the query into Excel. Yes, I know you should use Export but in the case of proposals Export doesn't provide the level of detail a Query export does.  With just a few steps I can create an Excel document that shows our donor pipeline, what's been received and what is expected when.  You should be able to get all of the data points you mentioned with the Constituent Query and more. 


    It's up to the gift officers to keep their proposal names accurate and change it when the gift comes in.  Since they get the results they want, they do make the changes.  Each MGO can run their own query at any time to see their pipeline so it's easy for them to update.       
  • Debra,


    Is your organization using the relationship module; if so are you finding the system ID for the proposal?


    Thanks,


    Jason 


     
  • Jason Rose:
    Debra,


    Is your organization using the relationship module; if so are you finding the system ID for the proposal?


    Thanks,


    Jason 


     

    I'm still curious/confused about why/how you tie Proposals to Relationships.  Can you enlighten me on what your link is between the two.

  • We are looking to export all of our proposals to another system, the constituent module gave me all the proposals in columns but I needed the rows


    So ---

    Constituent1 | Proposal1 | Proposal2 |
    But I need it this way:
    Constituent1 | Proposal1 |
    Constituent1 | Proposal2 |

    The relationship module was the only way I saw get the data in rows, I am open to suggestions, but I does not consistently export a unique identifier.

    The relationship module was the only way I saw get the data in rows. I am using the proposal section in the constituent tree. 


    Thanks,


    Jason 
  • Screen shot to describe where we are at. 90e8a65be46b24d90aab865352f09674-huge-pr
    2370fc2beadce789b8f443dbcc8bedd4-huge-pr
  • Is it easier to track proposals in NXT? My new org uses proposals but I have little experience tracking this info and/or using query and export to extract any information related to proposals. We do have NXT and it seems very easy to track "opportunities", so I wasn't sure if I was missing something. Thanks

     
  • Crystal Godbolt‍ - it is much easier to track proposals/opportunities in NXT but you don't have as many options for reporting. So on the one hand, finally if you export your Opportunities List, you don't have to clear out the junk --- but you can't export Opportunities with all the same amount of detail as you can get from a database constituent export.


    My team uses a combination approach of NXT for surface-level management and Query-export for more complex reporting, and we hope and pray that we never need to do something that requires Export-export. (But I do have one of those tasks coming up, and one of the ways we make it better is using both kinds of export and setting up concat formulas on the proposal fields with index/match in excel to put the system ID onto the query output, rather than fuss with the export formats. It's something I'm putting off as long as possible, because it's tedious and I always make a ton of errors before I get it right.)
  • Thanks all for this helpful thread.


    At a tangent - anyone seen good examples of pipeline reports pulling through from Proposal information? Oklahoma State did a great presentation at APRA PD 2016 showcasing their reporting suite and I wondered if there were other such examples.


    Thanks!
  • I created a crystal report that pulls all proposals with a status of "strategy" or "pending." They are grouped that way with dollar amounts asked totaled. Columns include constituent name, solicitor name, program name, amount asked, date asked and date expected. It's used at all of our prospect meetings and one-on-ones with gift officers.
  • Thanks Mark, that's helpful.
  • If you need the proposal id to do updates, then I use the Import feature, Create Import file.  You can use a query to narrows down your selection, although it will still give you extra records because it will dump all the proposals for the respective constituent ids rather than just the specific proposals you may have qualified in the query.  The flaw with this is you can't link other constituent or gift information with the proposal records.  Until Blackbaud makes the proposal id a field that is extracted or at least give in export utility to give additional and relevant extract criteria for proposal, if you are a shop with many proposals, there is no easy way to qualify the specific ones you want.  In NXt it is a bit better, but the output lists doesn't easily enable you to associate much constituent information with the proposals extracted.  

     

Categories