Adds the Text part of the Insert Text script step into the StepText, so it appears in the QuickFind.īaseElements 18.0.3 - Released 2nd September 2019.Removes the extended privilege for WebDirect.Updates the plugin to include a version that is signed and notarised by Apple for Mac OS Catalina support.īaseElements 18.0.4 - Released 11th September 2019.Fixes an issue with the links to fields used in Sorts.Fixes tab orders in the reports layouts.īaseElements 18.0.6 - Released 19th February 2020.īaseElements 18.0.5 - Released 18th October 2019.Fixes an issue with running the comparison report from an Analysis and the File list not showing up.Also added Script Tree for dependency tracingīaseElements 18.0.7 - Released 4th March 2020.Brought SQL into it's own location for more prominence.Temporarily removed the ThemeBuilder and Top Call log report, they'll come back in a future release.Improved layout of the Change report, with new copy functions.Added favourites that remain even if the solutions are deleted.Added ability to re-import only a solution, not all analyses.New sort to show latest import and group by Solution in the list.Returned the back/forward buttons to the main toolbar.WebViewer based location tab allowing hierarchies.Compatible with all the new functionality introduced in FileMaker 19 including script steps and functions.There were intermittent releases of v19 in beta and also later versions during 2021, but this was the first final release.If you'd like us to locate characters in a file of your own, please contact us with a support request.Version History BaseElements 19.4.0 - Released 10th December 2021. Then you need to understand how to find the location given the XML structure of the file. You need to run a validity checker in an XML aware app, like TextMate, BBEdit or OxygenXML. You can't use XML tools to process the file as it's invalid XML and so that won't work. How do I locate the characters in question? It would be best for the text to be cleaned up in order to know exactly how your solution will behave. It's more that there is unexpected low ascii text characters in text somewhere, that are probably not what you're expecting. But you may have strange issues copying and pasting them as the clipboard process also uses XML and so will also be invalid. No, we've not seen issues that are caused by these characters. Is this a problem, will it break my solution having them there? No, your FileMaker is not affected, just the DDR that is imported into BE. This way you can locate and repair them if needs be. We did this so that you have an idea of what was happening, instead of just silently removing them from the DDR. In BaseElements version 5.0.6 and later, with the 3.3.4 version of the plugin, we changed the process slightly to report the count of removed characters. Why is BaseElements reporting a count of changed characters now? They are usually in text on layout objects, or formatting options like currency symbols.īy removing them we can allow BaseElements to process them when they otherwise wouldn't import, and a HTML DDR doesn't work at all. ![]() The characters themselves are not critical to the operation of your solution or to analysing the DDR in all the cases we've seen. ![]() The BaseElements import process in 5.0.0 and later removes these characters from the DDR to enable it to process the import. ![]() ![]() The DDR process should be converting these to valid XML, but it doesn't always do this accurately. These are often layout characters or other text pasted from outside sources. Sometimes though, there are characters in the file itself that come out in the DDR as invalid XML. The FileMaker Database Design Report ( DDR ) is a report on what is inside your FileMaker solution, generated as XML. BaseElements removed characters in my DDR!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |