Milly Jones
My feedback
12 results found
-
32 votes
An error occurred while saving the comment -
49 votes
An error occurred while saving the comment
Milly Jones
commented
having to rebuild the same transformations over and over and over and over again is not only frustrating, but introduces a huge risk. If I forget to update one transformation, my formula is now wrong. Whereas with a saved transformation, I only have to update on transformation, and all the formulas using it are updated.
-
98 votes
An error occurred while saving the comment
Milly Jones
commented
this is critical. we have worked hard to get our address formats in the database up to date with Canada Post standards, and now they are being needlessly overwritten by Omatic Cloud formulas when the format is different, or duplicate records are being created.
Milly Jones
supported this idea
·
Milly Jones
shared this idea
·
-
1 vote
Milly Jones
shared this idea
·
-
197 votes
Milly Jones
supported this idea
·
-
3 votes
Milly Jones
shared this idea
·
-
3 votes
Milly Jones
shared this idea
·
-
1 vote
Milly Jones
shared this idea
·
-
1 vote
Milly Jones
shared this idea
·
-
157 votes
An error occurred while saving the comment
Milly Jones
commented
@Steve Brewer - no problem with updating the language. However, I am not sure "reusable" fully carries what I am I asking for. If I reuse a translation - it will become another instance of that translation - and therefore I am still left with having to update every instance of that translation when a new value needs to be added.
As this is a very frequent occurrance within our gift processing structure, with the ability to save one instance of a translation and apply that single translation to all selected formulas, using OC for our gift processing really becomes too much of a risk.
Milly Jones
supported this idea
·
An error occurred while saving the comment
Milly Jones
commented
Transformations are excellent, but having a single collection of transformations that I could apply on multiple formulas would be much more useful. Having transformations setup so that I can save them (possibly added to favourites?!) and reuse them would mean I just update 1 collection of transformations / favourited collection, instead of having to update multiple formulas with the same collection of transformations 5 or 6 times when I need to update the transformations to add a new value. Having to update each formula separately opens the door to items being missed, transformations being out of sync and errors in the database
-
2 votes
Milly Jones
shared this idea
·
-
78 votes
Milly Jones
supported this idea
·
many many many people go by multiple variations of their name. we need to be able to match on preferred name - why else do we record this information in the database!
In addition, CRA requires that we use their legal name on tax receipts, but we want to use their preferred name for communications. We want to ensure that their donations are matched to their constituent record, rather than duplicates being created because OC ignores other name formats