Stu Manewith
My feedback
15 results found
-
4 votesStu Manewith
supported this idea
·
-
10 votesStu Manewith
supported this idea
·
-
8 votes
An error occurred while saving the comment Stu Manewith
supported this idea
·
-
2 votes
An error occurred while saving the comment Stu Manewith
commented
This is still a fundamental issue with P2GL (including POM) and often requires client disappointment and unnecessary rework. And, even rework typically requires 'flying blind' since a larger volume of transactions are not available as sample data. In addition, clients get annoyed by being asked multiple times to refine their source data so that we can get the necessary sample on which to work.
An error occurred while saving the comment Stu Manewith
commented
I am still very much struggling with this issue. I'm working with a Strategic client who processes both online and offline gifts coming over from Salesforce -- but their current focus is processing offline gifts while we work out some kinks with online. The majority of gifts are online, so a skip row function removes them, but also removes all the sample data coming through -- and our P2GL filtering is not yet sophisticated enough to allow me to pull in only offline gifts. I really need some help here.
An error occurred while saving the comment Stu Manewith
commented
This is becoming a more pervasive and challenging issue as we continue to work with more Salesforce customers for Post-to-GL. Because of the need to skip rows within a formula because of inadequate front-end filtering, we don't get ANY sample data at all, and, therefore, need to run the formula and then examine the output, iteratively, in order to test and refine the formula logic.
Stu Manewith
shared this idea
·
-
4 votesStu Manewith
supported this idea
·
-
2 votesStu Manewith
shared this idea
·
-
26 votesStu Manewith
supported this idea
·
-
10 votesStu Manewith
shared this idea
·
-
7 votesStu Manewith
shared this idea
·
-
2 votes
An error occurred while saving the comment Stu Manewith
commented
Another less elegant option, which would still be an improvement, would be to output all data associated with a single transaction on a single row. Right now the data elements are segregated into 3 separated rows: first the basic j/e row data, then the project distribution and classification row data, and finally the transaction code row data. Troubleshooting errors would be easier if all of a transaction's data were output on the same row.
An error occurred while saving the comment Stu Manewith
commented
As we implement P2GL for more and more FE NXT clients, we need a better way to test our outputs. Most clients are live in FE NXT and don't have test systems; furthermore, there is no 'pre-post' option, when a formula is run, it creates a live journal entry batch in FE NXT. We need a way to look at a pre-post report or file or some other mechanism to see and validate (or refine) the results of FE NXT formulas before delivering them to the client. An option such as a .csv output file would be very useful.
Stu Manewith
supported this idea
·
Stu Manewith
shared this idea
·
-
1 vote
An error occurred while saving the comment Stu Manewith
commented
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.
Stu Manewith
shared this idea
·
-
2 votesStu Manewith
supported this idea
·
-
5 votes
An error occurred while saving the comment Stu Manewith
commented
'Between' would also be a very useful logic operator.
Stu Manewith
shared this idea
·
-
1 voteStu Manewith
shared this idea
·
-
2 votesStu Manewith
supported this idea
·
Stu Manewith
shared this idea
·
Thom -- that's a great idea. I've gone ahead and marked it as 'important'.