There's no bad use you can make of it, only good use
For me, FM Pro Advanced should come in two versions: the regular and the deluxe one, the latter having a FMPerception added to it.
I tested it - and bought it right after testing. It's the only analyzer that allows us to read DDR within seconds, we can really create a DDR (thats quite fast) all the time and run the analyzer (FileMaker based ones might take hours for reading a big DDR...)
FMPerception might be a little bit different than FileMaker based analyzers, but it's really effecticve, allows to export whatever one needs...
It's first impression I had, wow this is responsive...
Sent from my iPad
Tested it and bought it; a good addition to our tools. It doesn't replace the other analysis tools (for me) but I'm glad to have it for the quick checks.
Can you please elaborate on the functions or analyses of the other tools that it does not replace??
Can you foresee these limitations being overcome in a future release?
Not so much things missing, but a different way of doing things.
I work a lot with BaseElements for instance and there I enjoy the fact that I can write my own scripts to build certain subsets of data (for instance: give ma all the layouts with more than one portal,...). Or keep notes on the record iself.
In FMPperception you can't do that in the app itself, but you can export to excel and do the work there, so it's a different mindset really.
you can export to excel and do the work there, so it's a different mindset really.
you can even export and import in Filemaker
Very pleased with the speed of FMPerception and the new possibilities it offers to look quickly at the data about my own development.
I did write the accompanying AppleScript, so could be accused of being partisan.
However some of the other work I have been looking at has been re-energised by this tool. Working on a calculator for Cyclomatic Complexity of scripts, and being able to convert a layout into the code required to re-create the page with iText and ScriptMaster so PDF can be generated on Server for Go and WebDirect
Thanks everyone for the nice comments. We hope FMPerception will forever change the way you develop FileMaker solutions for the better.
Here is another quick tip. You can use FMPerception to quickly find the name of the Script by its Internal ID. This is very helpful if you are using FileMaker 15 Server Top Call Logging to find slow scripts, because the log only reports the ID of the script not the name.
If you have any questions, feedback or feature ideas, please send them to email@example.com