Omatic Cloud
13 results found
-
additional -- useful -- logic operators in P2GL
Can we add some additional -- useful -- logic operators to P2GL?
*Blank
*Not Blank
*Does Not ContainBlank and Not Blank are especially useful. Today, without them, we're forced to use 'Equal' or 'Does Not Equal' and then compare that to an unpopulated field. Sometimes, however, if there are spaces in a field, it might look to be blank but isn't really.
All and all, it's just safer and more efficient to have 'Blank' and 'Not Blank' operators.
'Does Not Contain' is useful for working against alphanumeric data, and would prevent needing to use more complicated 'If/Then' or 'True/False'…
5 votes -
Add/Update Gift Data as part of PostOmatic Processing
We often use PostOmatic (POM) to apply complex logic, concatenating data from multiple sources in RE to determine the final Debit/Credit accounts to which transactions should be written in our financial systems.
There is no simple way to look at a gift in RE and say, "This is the Debit/Credit that was used."
While the output data from POM can be re-imported to RE, currently, this is a secondary manual process. Could POM be updated to include an option for automatically adding the final Debit/Credit outputs to the source gift record?
4 votesThanks for the idea JPP. Can you be more specific about where you want the debit and credit used to be added back to the gift? There are certainly limitations as to where data could be written back to the gift due to field size constraints as well as considering all of the output that is typically in Post to General Ledger files.
Here are a few more questions for consideration:
What is the goal of having this data in RE/how would that data be used?
Should there be any considerations if an adjustment is being posted due to adjustments creating reversing entries to reverse out what was previously posted and then having new journal entries created for the updated information?
What other scenarios might we need to account for if we added a write-back feature?
Thank you
Steve Brewer
Product Manager
-
SFTP for P2GL
Please add SFTP capabilities for ingesting files from 3rd party CRM's to P2GL.
4 votes -
Post-to-GL: Create New Journal or Append to Existing Journal
The process of uploading a file to Post-toGL creates blank or incomplete JE in FE NXT if there are data entry errors in the document that cause the transaction import to fail.
Could the Post-toGL connection be updated to provide the options / ask the question if the user wants to:
- Create a New Journal Entry
- Append to an Existing Journal Entry
This update would reduce the number of empty or incorrect JE that have to be deleted from FE NXT.
3 votes -
Update FE NXT Batch Desicription on import error
Post to GL creates the JE batch and then progresses through importing the transactions. If a transaction results in an error, Post to GL stops the import process—however, it may have completed a partial import, and that partial import may be "in balance."
It would be helpful if, when Post to GL fails due to a transaction error, the JE batch description could be updated to append an error message so Finance is aware that the batch was not created successfully.
3 votes -
Print out P2GL formulas
Currently there is no ability to print out P2GL formula configuration or logic threads. Since formulas cannot currently be copied, they have to be replicated manually and the inability to print formula configuration tremendously hampers that effort. This is even true when working to apply logic from one client's formula to another -- since the logic thread cannot be printed, it's challenging to recreate from memory and/or to toggle back and forth between formulas/monitors, etc.
2 votes -
Sample Data (not enough of it)
Sample data provided when configuring new P2GL formulas is limited to 20 or 25 rows of transactions, which typically is not enough sample data to ensure that formula configurations are accurate and doing what the client needs. Two examples:
In one case there were transformations configured that looked right on the first 20 rows of data, but we couldn't see that the logic was incorrect on other rows. It was not until the client ran the post and saw an error on row 190 that we were alerted that the logic needed to be refined.
In another case, skip row…
2 votes -
P2GL Activity History
It would be helpful to have Activity History for Post to General Ledger formulas. This would allow for an audit trail when trying to troubleshoot errors or instances when a formula was work previously and is no longer working.
2 votes -
On the Post to GL 'View History' screen, add a column that shows how long a job took to run
On the 'View History' screen, can we see how long a job took to run?
Having the duration data would help clients be able to gauge the duration of future posting processes and even when they should be kicked-off, etc.
Eg, if running 9K records took 80 minutes, and my next posting is 13K records, I should plan for it to take around 2 hours, etc.
1 vote -
Post to GL outputs for FE NXT
The formula template for posting to FE NXT does not furnish any options for the output files that the formula generates (other than the actual batch in FE NXT). Since a Post-to-GL user may not have direct access to the destination FE NXT system, those output files are very valuable for analysis and troubleshooting.
Currently, they come out as .txt files, which makes analysis challenging even when using an advanced editor. Can the output file that represents the created FE batch be output in .csv format? Or, could the user building the formula be given an option for the format…
1 vote -
Which FE NXT batch(es) errored out?
With the new batching mechanism that can generate multiple FE NXT journal entry batches at once, we need the ability in the error text file to identify problematic batches. That way, we can delete those and leave the rest. Right now, it’s hard to tell which batches are broken.
1 voteWe already have plans to update error messages when a journal entry cannot be created and FENXT returns an error to include the Batch ID in the error message so that the user has more information.
-
Audit trail on P2GL formulas
We need a way to identify who (which user) created and last changed a P2GL (including POM) formula. We also need an audit trail to identify who may have deleted a P2GL formula.
1 vote -
Post-to-GL prepost feature
Many Salesforce and Virtuous clients who have FE NXT but migrated from RE NXT are used to the 'prepost' feature in RE / FE integration.
P2GL for Salesforce or Flat File does not have a similar feature that can be used to validate a posting before it creates an open J/E batch in FE NXT. A number of clients have asked about this.
1 vote
- Don't see your idea?