Highlights of new functionality in Inspector Pro 3.1
There are a number of things that we did to improve Inspector 3.1. One of the main goals was to explore using data visualization to help "See the Big Picture". We focused on new features:
Here is a comprehensive list of additions, fixes and updates in Inspector Pro 3.1:
FIXED Something broke recently in regards to being able to use the comparison feature - (fixed this so comparisons are now working again)
FIXED Trace Script report window was not navigable nor closable
FIXED A bug where Inspector was not finding scripts that were no longer attached to buttons
FIXED A bug where Inspector where inspector was reporting an external file missing at times
FIXED Added Install Menu Set - script step in step list popup menu as it was missing but was available from the steps view
FIXED Added Install OnTimer Script - script step in step list popup menu as it was missing but was available from the steps view
FIXED Value List Dependencies Report - External value lists were not showing database
FIXED Relationship Dependencies Report (To Database) corrected to reflect where the item is coming from
ADDED Value List Dependencies Report -the External Data Source used for an External Value List
ADDED In the Overview item names are linkable (in blue) they will navigate you to the area of the database ( same functionality of the popup menu )
ADDED In calculation dependencies when showing a field dependency added the table occurrence name of the field
ADDED A new Detection - Check for Duplicate Script Names
ADDED A new Detection - Check for Duplicate Layout Names
ADDED A new Detection - Check for Unstored Calculation Fields on Layouts ( could provide some performance improvements )
ADDED A new Detection - Check for Summary Fields on Layouts ( could provide some performance improvements )
ADDED A database specific Security Perspective Report for Basetables
ADDED A database specific Security Perspective Report for Fields
ADDED A database specific Security Perspective Report for Layouts
ADDED A database specific Security Perspective Report for Scripts
ADDED A database specific Security Perspective Report for Value Lists
ADDED A Script Universe ( Force Directed Graph ) for all scripts in your solution ( mac only, on windows this requires the use of FireFox )
ADDED A Script Universe ( Force Directed Graph ) for a single script your solution ( mac only, on windows this requires the use of FireFox )
ADDED A Detection Option under script steps - to detect local memory variables that have been declared but not referenced
ADDED A Detection Option under script steps - to detect local memory variables that have been declared but not referenced
ADDED A Detection Option for Calculations to check for Suspect Calculations
-----------------------------------
When the DDR xml is generated for each calculation FileMaker outputs a set of Chunks for breaking down the calculation into the component parts of what it is made up of. Here is an example of some of those component parts:
<Chunk type="FunctionRef">Case</Chunk>
<Chunk type="NoRef">( </Chunk>
<Chunk type="FunctionRef">GetAsNumber</Chunk>
<Chunk type="NoRef">(</Chunk>
<Chunk type="FieldRef"><Field table="Calendar" id="4" name="Day 1"/></Chunk>
When calculations don't have any problems, chunks are output and Inspector looks at each chunk of the calculation and provides you with a great way to see what and where things are referenced.
However there are times when FileMaker will not generate the chunks. There most likely is a problem with your calculation, for example a field might be missing. But you might also be looking at the calculation and it looks totally fine. If you were to try to click Ok to calculation dialog you would, however get a warning that there is something wrong with your calculation. It could be the context is incorrect or it could be that the relationship that existed before for related fields that you were using in your calculation has been deleted and now there isn't a valid relationship to get to your calculation evaluated from. When FileMaker goes to output the DDR for this field it will not generate any chunks for it. This is what we look for and it indicates to us that there may be a problem when this calculation is evaluated.
-----------------------------------
Example of a Script Universe for an entire solution:
![]()
Example of a looking at Script References to a single script:
------------------------------------------
------------------------------------------
Allows you to see all the dependencies that a calculation relies on. Click on any node (represented by a circle at the base of any branch) and you can expand, or collapse that branch. You can also zoom in or zoom out and "See the Big Picture" as to how your calculation works:
![]()
Added a Script dependency view (interactive tree view)
-----------------------------------
Allows you to see all the steps that a script might take. Similar to the trace report except that you can expand, collapse, zoom in and out. Get the big picture of what your script structure looks like. You can also to choose to only output the scripts so you can get the bigger picture.
![]()
Highlights of new functionality in Inspector Pro 3.0v2:
*Note: A 5-user Inspector Pro "Team License" is available at a significant discount through the Beezwax Store.
Inspector Pro 3.0v2 is available as a free update for v3.0.x owners via the Inspector Pro Download/Demo page.
Here is a comprehensive list of additions, fixes and updates in Inspector Pro 3.0v2:
Comments