Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FM Not Honoring Namespace in XSL

Featured Replies

FileMaker is complaining

"XML parsing error: Attribute 'xmlns:cm' is not declared for element "FMPXMLRESULT".

But it is declared. I begin my XSLT sheet with

xmlns:cm="urn:schemas-Professional-Plug-in:P2:ClipMetadata:v3.0">

Still, when I prefix any node reference with "cm:" For example,

FMP 8 complains the prefix has not been declared. The XSLT does work in every parser I've tested, including Test=XSLT. It is only FMP that complains.

I've even tried a second declaration here:

0

But FMP refuses to inherit that xmlns:cm declaration, calling it an undeclared attribute.

Any ideas?

Maybe the error means the opposite, maybe it means that FileMaker cannot import elements with the "cm" prefix in the resulting xml. Try this:

Yes, namespaces, though supposedly self-evident, often seem mysterious, until you get it to work :)-]

  • Author

That was it! A case of the error message reporting the wrong error. Works like a charm now. Thanks.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.