Make the proposal/opportunity import ID filed available in query

Updating proposals/opportunities by clicking into them one at a time is not an efficient method when mass updates need to be made to several proposals quickly. The proposal/opportunity import ID enables the unique identification of proposals, allowing them to be quickly downloaded from a query with key fields, to be reviewed and updated within a spreadsheet, and imported back into RE with the new information. The current method for extracting the import ID for proposals/opportunities involves creating an import file and filtering out the necessary records for review, which is time-consuming. This approach only provides the constituent's ID without any constituent name fields, which must be matched and added using MS Access or other matching methods. I am currently adding the proposal import ID to attributes/custom fields using default sets to automatically generate the beginning number sequence of the proposal import ID (00010-589-000000), saving the record, and right-clicking on the proposal properties for the proposal to find the new import ID. I then add unique numbers to the end of the import ID sequence (00010-589-0000005555). This manually added Import ID enables me to download proposals that were not funded by the end of the previous month, as expected, and add new expected dates to all of them, pushing them to future dates for multiple proposals simultaneously.

  • Jenifer Harmen
  • Jun 17 2025
  • Reviewed: Voting Open
  • Attach files
  • Guest commented
    September 19, 2025 21:32

    YES!

  • Guest commented
    September 03, 2025 17:51

    My proposal query is pulling very specific proposals, ones that were denied or funded only in the previous fiscal year, so that I can inactivate them.

    Many of our records currently have multiple proposals (inactive and active), so if I use the query in export, export only looks at the constituent and not the very specific proposals that I am attempting to update to inactive with the proposal import ID. The results I get show the proposal names, whether they are active, and the import IDs for them all.

    Then I have used VLOOKUP to find the proposal names and return the corresponding correct import ID. Sadly, our legacy system also had the same generic proposal naming convention for all proposals (Proposal #01-1, for example). So all of those proposal import IDs I had to look up manually on every constituent's record.

    I did try to use only 1 import ID in Export, but I did not always get the correct import ID. Just in a few spot checks, I found 2 import IDs that should not be included, because those proposals are in a stage that was not included in my query criteria. Also, I found 3 constituents that were only listed once with one import ID, but they all have 2 proposals in my query that I need to inactivate, so those other import IDs are missing from Export. Therefore, I had to use the VLOOKUP with 10 import IDs exported option to ensure that I was getting the correct import ID for accuracy's sake. If the Proposal Import ID could be added to Query as an Output option, it would alleviate these errors and the time it takes to correct them.

    I need to be able to inactivate all of the proposals in the original query.

    I would not be able to narrow down the selected proposals, because the proposals I need the import ID for vary widely between all of the available selections, and there are going to be some constituents who have more than one proposal that I need to inactivate from one or more of these selection options.

    Export does not output the exact proposal import ID that I need from the original query, since it is only pulling constituent records, (but there is no Proposal Export option available, nor is there a proposal query option, so I must use a constituent query and Export), and if I only output 1 proposal, Export overlooks proposals if the original query has more than one proposal on a single constituent. Hence, the need for the Proposal Import ID to be an output option in query.

    Therefore, it would be greatly appreciated if the proposal import ID were available in query as an output option, just as Proposal Notes and Proposal Attributes have Import ID's available in query.