Skip to content

Omatic Cloud

Welcome to the Omatic Cloud feedback forum. Do you have an idea to improve the product? Do you recognize a good idea when you see one? You can create your own ideas and also vote on existing ideas. We want to hear from you!

7 results found

  1. Post Salesforce Payments in Post-to-GL

    My current understanding is that the P2GL API for Salesforce does not allow posting of payment records that are not themselves SF Opportunities, eg, pledge payments (ie, the pledge is the Opportunity, and payments are payments against the pledge but not Opps themselves. We need to be able to post payments that are not Opportunities.

    When considering pledge fundraising and the ability to properly account for pledge payments against pledge commitments, the payment, and not the opportunity is the fundamental basis for pulling Salesforce data.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Post to GL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Ability to filter Salesforce Donations for Posting based on a Salesforce Report (Query)

    Currently, the only filters available for gathering Salesforce donation transactions for P2GL posting include Stage, Campaign, and first-class Date fields on the Opportunity object. Very often, clients have data in other objects in Salesforce that drive the post process. (Payment object and custom object data elements are often needed for filtering.)

    Ideally it would be nice to be able to export transactions based on a Salesforce report (query). This would only work if there were less than 2000 records due to the limit that Salesforce imposes, but clients could control the records appearing in the report themselves by posting more…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Post to GL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. pull pledge payments on pledges with multiple payments

    make payments the center of the decision of data to post instead of opportunities

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Post to GL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. POM/P2GL: Summarize Filtered Rows

    POM/P2GL can summarize transactions, creating a GL import file that contains 1 bank line and X revenue lines. This functionality is applied at the configuration level - and, therefore, impacts the entire file output.

    We don't currently have a way of identifying selected transactions (e.g. Adj/Rev) where we do not want these summary transactions to be applied.

    I'd like to see the ability to apply filters to the summary criteria to help drive when the summary should be applied.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Post to GL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi JP,


    Thank you for submitting the idea.  I wanted to make you aware that Post to GL currently supports this use case and summarization can be configured to summarize some transactions and not others.  The only requirement is having the information available in the source data to be able to configure the scenarios needed.


    I know I have seen clients have formulas configured with the following scenarios:

    1.  Summarize non-adjustments but not adjustment transactions

    2. Summarize debit transactions but not credit transactions

    3. Summarize specific account numbers but not other account numbers

    4. Summarize transactions for specific funds but not other funds


    There are definitely others that could be considered.

  5. Post to GL: Logic Actions/Drop Down Options

    It is possible to put the logic actions/drop-down options in alphabetical order?

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Post to GL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    completed  ·  Emily Dalton responded
    You can now see that these have been implemented when you log into a Post to GL Formula
  6. Copy and delete P2GL formulas (including POM formulas)

    It would be incredibly helpful to be able to copy P2GL formulas. There are several use cases, but they generally boil down to the need to test or experiment with P2GL functionality while not upending configuration work that's already been built and may even be in production. Less important, but still useful, is the ability to delete P2GL formulas that failed or that are no longer active/useful/viable.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Post to GL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Opportunity Record Field in Salesforce NPSP

    The Opportunity Record Type in Salesforce NPSP is akin to Gift Type is Raiser's Edge NXT.

    Currently, the Salesforce the NPSP Opportunity Record Type field is only exposed in P2GL for use in formula logic and output via the Record Type ID. The Record Type ID provides a more cumbersome way of applying field logics. In addition, it requires a Salesforce user to have admin access to identify the Record Type ID for the respective Record Type labels.

    It would be very useful to have the label exposed for the Opportunity Record Type, not just the field ID to facilitate…

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Post to GL  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Omatic Cloud

Categories

Feedback and Knowledge Base