Adding Solicit Codes on demoted records

Venky Immadisetty

Hi,
Good Morning!

We are storing the demoted records in list management and trying to update the Solicit codes and request no email (check box is true) for those records through power automate. I am able to get the Solicit codes for demoted records from list management (Import Omatic)

but unable to create the new solicit codes. When I am trying to create the Solicit code it throws below error
error:[{"message":"The requested resource could not be found.","error_name":"ResourceNotFound","error_code":404,"raw_message":"The requested resource could not be found."}]

Is it possible to create the solicit codes for demoted records using power automate?

Dariel Dixon

I'm not sure what you mean when you say “demoted records” @Venky Immadisetty. I don't think you are turning them into non-constituents, because non-constituents can't have solicit codes.

Austen Brown

@Venky Immadisetty - I anticipate this error is based on how demoted constituents are stored. I'm not familiar with the specifics of how List Management is structured, but Omatic may be able to help you get to the bottom of this.

Venky Immadisetty

@Dariel Dixon
Yes we are converting them into non-constituents

Alex Wong

@Dariel Dixon
I think he does mean non-constituent record

Omatic List Management is a tool to manage non-constituent record, even being able to create “un-related” non-constituent record to use as “prospect”. In RE app (database/webview), a non-constituent can only be created being associated with a constituent record: event guest; relationship, etc. Non-constituent does not have ability to have full-fetch constituent related info, such as gift or solicit code. However, Omatic, knowing full well how RE data is stored in the database, is able to store info that's not normally allowed by RE into the database table.

SKY API is actually able to get non-constituent record info by the system record id (yes, non-constituent also have constituent system record id), My guest is: SKY API endpoint to list constituent solicit codes by constituent system record id without caring if the system record id is actually a constituent or non-constituent, by querying the database table CONSTITUENT_SOLICITCODES to list out the code.

However, to create solicit code is a totally different situation and NOT allowed by the SKY API. IF blackbaud were to allow it, Omatic List Management wouldn't be useful anymore. AND if Blackbaud were to allow it, then “prospect management” will no longer take up valueable Record Band on RE NXT, reducing the need for org to pay more for higher Record Band. (highly doubt this will happen).

Alex Wong

@Dariel Dixon
In case you are wondering, RE database table stores both constituent and non-constituent in the same database table call RECORDS.

Amy Barker

@Venky Immadisetty I don't believe you can do this, as demoted records don't really count as full records, and as someone mentioned above, solicit codes can't be added to non-constituent records. Check with Omatic support for verification though!