Sync solicit code end-dates between NXT and DB view

NXT allows a user to put an end-date on a solicit code, which is very handy. However, solicit codes with an end date still show as active on the Database View record. This is a major issue, where even if end-dates are not available in DB view, the solicit code should no longer be present.


Additionally, you cannot pull a list in NXT of what solicit codes have end dates - making it a huge pain to try and decipher which codes are actually active and not when pulling queries.


Why have a field available that doesn't talk properly with DB view and is unavailable to search on?

  • Ellie Stair
  • Mar 22 2023
  • Will not implement
Constituents
  • Attach files
  • Keleigh Allen commented
    04 Jun 17:21

    The start and end dates should be added to web view queries as fields available for using as criteria as well as in the single row query export that will be replacing database view export.

    Attachments Open full size
  • Hillary Cote commented
    August 29, 2023 19:43

    This is huge. I find myself just deleting the solicit codes, anyway, so that they are reflected the same way in database view, where we do our work.

    Attachments Open full size

Related ideas