DamageDetectoR is a macOS-only tool that will help identify those issues that occur from time to time in an XML DDR which would cause the DDR to fail the import. While these issues typically do not cause database corruption or failure of the database to run, they do hinder our ability to view the scripts and layouts and other items within our file in FMPerception.
A Specific Focus
- Bad Characters – It is possible to paste a character into some calculation or layout object that you couldn’t normally type into FileMaker. These include non-printing (lower) ASCII characters such as a NULL or a vertical tab. These characters are not encoded by FileMaker, and result in bad characters. Damage DetectoR can find these.
- Corrupted Lines – Sometimes a FileMaker object will become slightly corrupted, which effects only the XML that is formed. In this case a tag in the XML is not closed, causing XML parsers to fail. DamageDetectoR can find these as well.
- Over 10MB – Some settings in FileMaker can produce a block of text that is over 10mb. DamageDetectoR will identify those issues.
After identifying the issue, DamageDetectoR shows where the issue is located, as specific as the object on the layout.
Also published on Medium.