364 results found

1. be able to define "Run Once" to within hours or minutes - not only days

   sometimes a gift gets accidentally deleted, so we have to use the "Run Once" function to re-run teh formula. It would help if I could run it for just exactly that single transaction I need to import, rather than a whole day of data which could be thousands of gifts

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Add Multiple Notes to One Action

   Need the ability to add multiple notes to one action. Existing IOM profiles have many notes per action sometimes, and the ability to replicate this in OC would be helpful.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Allow for the Import of Gift Aid Declarations in Omatic Cloud

   Absolutely critical for clients in the UK doing any gift importing. This is a feature that is UK specific but needed to move IOM profiles to OC.

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  3 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Ability to Import Mapping on completed formulas

   It would be great to be able to import a mapping into an existing/completed formula. Right now you can only do this if the formula is in "Draft", but there are many times where we need to be able to import a mapping to a completed formula. The workaround is "Copy and Swap", but that only works in some cases.

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Allow In-Line Edit in Formula Exceptions

   It would be helpful to have the ability to fix matching formula exceptions using inline edits. Specifically with email connectors, this is would be useful to correct invalid email addresses.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Match on preferred name in NXT !

   We need to be able to check incoming first name against both 'first name' AND 'preferred name/nickname' fields. THIS IS CRITICAL and is causing a much inefficiency and possible data corruption.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Support for line break character (/n)

   Right now we can add line breaks through Concatenation, but there isnt a simple way to force a line break in some more complex situations.

   We use this particularly for notepad text, where we want to summarise a few cells of data into a single notepad, e.g.

   'Signed up for Email Newsletter on the website. /n
   First Name Provided: Alex /n
   Surname Provided: Bishop-Thorpe /n
   Email address provided: alex.bishop-thorpe@'

   Importimatic supported '/n' as a line break character, but this isnt supported by Omatic Cloud. Instead it just renders the text '/n'. If we use the line break as the separator for the concatenation, we get this:

   'Signed up for Email Newsletter on the website.
   First Name Provided:
   Alex
   Surname Provided:
   Bishop-Thorpe
   Email address provided:
   alex.bishop-thorpe@'

   Which is acceptable, but not super readable.

   It does appear that if we import an excel document with like breaks in the cells (e.g. excel formula =CHAR(10)) it will honour these line breaks in the import. However, if we try to copy-paste this ASCII character in as a field when we concatenate, it gets filtered out.

   Can we have a way of forcing a line break in notepad text, like in Importomatic?

   Right now we can add line breaks through Concatenation, but there isnt a simple way to force a line break in some more complex situations.

   We use this particularly for notepad text, where we want to summarise a few cells of data into a single notepad, e.g.

   'Signed up for Email Newsletter on the website. /n
   First Name Provided: Alex /n
   Surname Provided: Bishop-Thorpe /n
   Email address provided: alex.bishop-thorpe@'

   Importimatic supported '/n' as a line break character, but this isnt supported by Omatic Cloud. Instead it just renders the text '/n'. If we use the line break as the separator… more

   5 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Custom Routing to send some rows onto another Formula

   Sometimes it's necessary (or more convenient) to achieve our desired outcome by taking one file and running two different Formula across it.

   A common example would be files that have a mix of Individual and Organisation records. One Formula for the Individual import, and another formula to do the Organisation import - the Organisation import would add and link the individual as a Contact against that Organisation. Fancy.

   Right now custom routing lets us skip some rows, having the Formula ignore them. This let's us have our two import formulas, one for Individuals and one for Organisations.

   But it would be amazing if Custom Routing could take those skipped rows and send them to the second formula. You run the file on the Individual formula, and then the rows that have Organisation data get sent to the second formula automatically. Both imports run, you get your desired outcome and your formulas are much cleaner to document and maintain.

   Sometimes it's necessary (or more convenient) to achieve our desired outcome by taking one file and running two different Formula across it.

   A common example would be files that have a mix of Individual and Organisation records. One Formula for the Individual import, and another formula to do the Organisation import - the Organisation import would add and link the individual as a Contact against that Organisation. Fancy.

   Right now custom routing lets us skip some rows, having the Formula ignore them. This let's us have our two import formulas, one for Individuals and one for Organisations.

   But it would… more

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Add individual system Record ID as a match option when importing a Relationship

   Expand the matching logic for Relationships to include the Constituent System record ID . The constituent system record ID is unique across RE and is assigned to a record once added in RE. This data point will allow the import for Relationship records to use an alias/alias type and constituent system record IDs to get an exact match and will prevent duplicate/reciprocal relationships to be added in RENXT. Currently ImportOmatc will match on an Alias ID and will not create additional relationships if it exists.

   Currently in OmaticCloud, matching on alias id/type will result in unwanted/duplicate relationships added to RENXT. Additionally, the current option in OmaticCloud for mapping in the Relationship section of a Profile is System record ID. This ID is associated to the relationship record in RE, not the constituent you match too.

   Expand the matching logic for Relationships to include the Constituent System record ID . The constituent system record ID is unique across RE and is assigned to a record once added in RE. This data point will allow the import for Relationship records to use an alias/alias type and constituent system record IDs to get an exact match and will prevent duplicate/reciprocal relationships to be added in RENXT. Currently ImportOmatc will match on an Alias ID and will not create additional relationships if it exists.

   Currently in OmaticCloud, matching on alias id/type will result in unwanted/duplicate relationships added to RENXT.… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Allow mapping to gift subtype and gift code for pledges

    Allow mapping to gift subtype and gift code for pledges. I currently get a message that this in unavailable for pledges.

    •  

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Ability to import gift note

    Currently I cannot import a flat file of gifts into an NXT/webview batch because I want to add a gift note.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Transformations: Completely delete/remove data field

    I would like to see that one of the transformations have the ability to completely delete/remove that field. One of the examples that I have come across is for consistuency codes. We use them if someone is giving at a certain amount annually. But if they are not at that level anymore, we need to delete the code. But I can see this being used for attributes or duplicate pieces of contact information.

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Link Multiple External System Accounts to a Single Salesforce Account

    If, over time, a donor makes gifts through Fundraise Up (FRU) using different email addresses (e.g., intially from an @aol.com account and later from an @gmail.com account), FRU will create a new record for the second gift. Because FRU isn’t a CRM, we can’t merge records. They will forever be separate with their own Fundraise Up ID (FRU ID).

    When we sync records from FRU to Salesforce, we can match the new FRU account to the old account based on a name and address match. However, this is a manual process and forces us to decide which FRU ID to keep in Salesforce. Ideally, once we’ve made the match between two (or more) different FRU accounts and a single Salesforce account, we'd like to store both (all) FRU IDs in Salesforce. To associate multiple FRU IDs with an Account (i.e., a many-to-one relationship), I presume that we’d need to create a separate object for FRU ID.

    In brief the workflow would look this:

    First Gift
    * Donor gives to FINCA using Email A.
    * Fundraise Up creates a record with unique ID.
    * When syncing to Salesforce Nonprofit Cloud (CRM), we create a new donor record and send all details (name, address, email, FRU ID).

    Second Gift
    * Same donor (same name and physical address) gives again, but uses Email B.
    * Fundraise Up treats this as a new person and creates a new record with a new ID.
    * When syncing to Salesforce, we want the system to:
    - Find the existing donor record (match on name and address).
    - Update the email to include the new one.
    - Store both fundraising system IDs (old and new) in the CRM.

    If, over time, a donor makes gifts through Fundraise Up (FRU) using different email addresses (e.g., intially from an @aol.com account and later from an @gmail.com account), FRU will create a new record for the second gift. Because FRU isn’t a CRM, we can’t merge records. They will forever be separate with their own Fundraise Up ID (FRU ID).

    When we sync records from FRU to Salesforce, we can match the new FRU account to the old account based on a name and address match. However, this is a manual process and forces us to decide which FRU ID to… more

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Salesforce  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Shopify Connector

    It would reduce a lot of manual work to have a connector to pull purchases from Shopify into RE NXT via a connector.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    started  ·  AdminSteve Brewer (Product Manager, Omatic) responded

    Hi Alexandria. Thanks for your idea. We currently have the Shopify in development. It should be ready to go in the new year.

15. Pull the correct names for a tribute match

    When importing tributes from Luminate Online, the tribute name pulls as the donor's name, so I have to go into the RE NXT record and the Tribute donation interaction to see the incoming data and match it to existing data. Once the tribute goes into RE, the Tribute name shows as the correct tribute name indicated on the form, so it would be nice if the correct name showed up on the import screen.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. View API Name in Object Picker

    When selecting fields in the Object Picker, some of them have the same label but different API names. For example, we can have City (MailingCity) or City (City_Employer). It would be extremely helpful if we could hover over the field and see the actual API name to ensure we're mapping to the right field, rather than needing to do a lot of trial and error testing.

    2 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Salesforce  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. katrina.molnar@mercy.net

    Currently when using the Classy Connector in O-Matic Cloud and building/updating a formula, you are unable to add a new "Campaign Type" when "Editing Classy Settings" in a profile without all of the previously selected campaigns disappearing. This forces the user to have to reselect all of the campaigns wanted in the profile. My organization 171 active campaigns. It would be great if users could select a new Campaign Type without all of their previous selections disappearing in the formula build.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Add "Single" as option for Schedule Frequency for Pledges

    It looks like Blackbaud has added "Single" as an additional option in their SKY API for schedule frequency in the Gift API call. The full list of options for frequency is now:

    "Annually",
    "EVERYSIXMONTHS",
    "Quarterly",
    "Monthly",
    "EVERYFOURWEEKS",
    "EVERYTWOWEEKS",
    "Weekly",
    "Irregular",
    "Single"

    Can the API call be updated and coded in Omatic to accommodate the new options for mapping this field?

    https://developer.sky.blackbaud.com/api#api=gft-gifts&operation=CreateGift

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Fuzzy Organization Name Matching

    Currently, Omatic Cloud does not support fuzzy name matching for organizations. Organizations can only be matched on name exactly. In this case, if you were to try and import employment data, minor variations in organization name will force you to manually match with existing organizations or you will end up with multiple duplicate organizations within your database. Fuzzy organisation name matching would make this process much simpler and streamlined.

    18 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Allow defined type property for the column

    The table, when it doesn't explicitly know the data type of a column, defaults to sorting its values as strings. This causes numbers to sort incorrectly (e.g., '10' appears before '2'). For proper numerical or date sorting, the table requires either a defined type property for the column (e.g., type: 'number') or a custom sort function that understands how to compare the specific data type.

    3 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Raiser's Edge NXT  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating