Reporting on Opportunities in NXT (or Proposals in Database View)

Ken Willey

Hello!

Unfortunately, it appears that opportunity lists in NXT cannot be exported with complete constituent information (ID, address, etc.).

Meanwhile, in the database view, there's no export type of “proposal” (i.e., opportunities are apparently called “proposals” in the DB view). You can export X number of proposals in the output, but it will just include all the proposals in can, and not necessarily the ones we're interested in (the criteria that can be set for proposals within the export is minimal).

I thought that perhaps I could take an export from NXT (with the opportunity info) and join it to an export from the database (with the detailed constituent information) in Excel. However, because the NXT list export doesn't have any 1:1 identifying information (like Constituent ID), I can't do that.

Has anyone else encountered this issue?

Thanks a lot!

Marie Stark

It looks like the Opportunity export includes the System Record ID. I believe in Export you can also export the system record ID of the proposal. It's not ideal but maybe you can connect them using the system record ID.

Karen Diener

Ken Willey:

Hello!

Unfortunately, it appears that opportunity lists in NXT cannot be exported with complete constituent information (ID, address, etc.).

Meanwhile, in the database view, there's no export type of “proposal” (i.e., opportunities are apparently called “proposals” in the DB view). You can export X number of proposals in the output, but it will just include all the proposals in can, and not necessarily the ones we're interested in (the criteria that can be set for proposals within the export is minimal).

I thought that perhaps I could take an export from NXT (with the opportunity info) and join it to an export from the database (with the detailed constituent information) in Excel. However, because the NXT list export doesn't have any 1:1 identifying information (like Constituent ID), I can't do that.

Has anyone else encountered this issue?

Thanks a lot!

I've had to do this in the past, well before webview was on the horizon. And I think that process is still the best way, regrettably.

I did a constituent query to get my Proposals (Opportunities in NXT) and included Cons ID in the output. You will get every single proposal on a record unless you can specifically filter out the ones you don't need. Regardless, export that to Excel and remove Proposals if necessary.

Then I ran my mailing list portion via export - to get the address and other constituent info.

The last piece was to do VLOOKUP or a join in Access to append the Proposal data to the mailing list.

Maybe someone else has a better way!

Karen

Dan Snyder

@Ken Willey For our proposal reporting, we actually export proposal information from the query output in database view (I know not BB recommended, but it works). You can select the preferred address as an output option.

The two caveats is that it will not export the Proposal ID, so for our purposes I just concatenated the constituent id and proposal name to make our own ID. Also, if you were to export actions you will get duplicates if there is more than one action.

We actually have our gift officers record their next steps for each proposal/opportunity as proposal notes and if there is more than one proposal and/or note I have a process in Power BI (can be run in Power Query) to remove the duplicates and only keep the most recent note. Happy to chat more about that if you wanted.

Jennifer Vincent

As @Dan Snyder said, I always exported proposals from query. It was the one exception to the rule of “never export a query” because it was the only way to get out the information in a useful format. You can export the system record ID from webview and from query, and join them from there with xlookup in excel to more easily capture the next action data. In order to get those in a single report out of database I had to rely on a custom crystal report from years ago. I eventually gave up on that and would just pull up NXT during reviews to work from within the database.