Jump to content
Sign in to follow this  
ggt667

When exporting XML as fmxmlresult.xml when does FilMaker populate the content of the layout attribute?

Recommended Posts

Posted (edited)

When exporting XML as fmxmlresult.xml when does FileMaker populate the content of the layout attribute?

Usually it looks like

<DATABASE DATEFORMAT="D/m/yyyy" LAYOUT="" NAME="Menu.fp7" RECORDS="51" TIMEFORMAT="k:mm:ss "/>

Yet sometimes it looks like this

<DATABASE DATEFORMAT="D/m/yyyy" LAYOUT="menu" NAME="Menu.fp7" RECORDS="51" TIMEFORMAT="k:mm:ss "/>

Then again when querying the XML RPC it always look like this

<datasource database="Menu.fp7" date-format="MM/dd/yyyy" layout="menu" table="Menu" time-format="HH:mm:ss" timestamp-format="MM/dd/yyyy HH:mm:ss" total-count="0" />

Asking the question myself, answering the question myself as well. Checking the following checkbox populates the LAYOUT-attribute of FMPXMLRESULT

FMXMLRESULT LAYOUT populate.png

Edited by ggt667
Solved

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Who Viewed the Topic

    1 member has viewed this topic:
    Lee Smith 
  • Similar Content

    • By the Otter
      I’ve got a FM16 system that converts raw data (dimensions, etc.) into a SVG floor plan and elevations in the Web Viewer. However, my boss now needs me to use this same data to generate a DXF for integration with another system. Has anyone had experience doing this? I’ve been reviewing the DXF specifications, and it seems unfortunately nontrivial to me. Any guidance would be appreciated.
      Thanks so much!
    • By Olypatchmaster
      Our network person and I have done a bunch of troubleshooting and came up with this summary and a few questions.
      Ever since we installed FileMaker 16 in our two-machine setup, Zulu has been failing. In the Zulu error log from C:\Program Files\360Works\Applications\logs:
      Oct 2, 2017 8:44:59 AM PDT com.prosc.mirror.config.server.FileMakerServerInfo getHostAddressForProperties
      INFO: Will use 127.0.0.1:16020 for direct WPE address.
      Oct 2, 2017 8:45:05 AM PDT com.prosc.fmpjdbc.FmXmlRequest doRequest
      INFO: Starting request: http://127.0.0.1:16020/fmi/xml/FMPXMLRESULT.xml?-db=DatabaseName&-lay=ProscNoSuchTable&-view
      Oct 2, 2017 8:45:05 AM PDT com.prosc.fmpjdbc.FmXmlRequest setProductVersion
      WARNING: Null product version; assuming 12
      Oct 2, 2017 8:45:05 AM PDT com.prosc.fmpjdbc.FileMakerException <init>
      INFO: com.prosc.fmpjdbc.FileMakerException: Error 959: XML Web Publishing is not enabled - Run the FileMaker Server deployment assistant and make sure that the XML web publishing checkbox is selected () username: domain\user / requestUrl:http://127.0.0.1:16020/fmi/xml/FMPXMLRESULT.xml?-db=DatabaseName&-lay=ProscNoSuchTable&-view

       I verified that the URL does indeed return an error code of 959. Playing around with it, I found that if you use the DNS name of the machine instead of the localhost IP:port (https://wpe.domain.edu/fmi/xml/FMPXMLRESULT.xml?-db=DatabaseName&-lay=ProscNoSuchTable&-view), the request returns an error 105 (expected response) instead. 
       
      I poked around on the internet trying to find out more about this, and discovered the -dbnames command; again, it works fine on the main https port (https://wpe.domain.edu/fmi/xml/FMPXMLRESULT.xml?-dbnames), but returns a 959 on the Custom Web Publishing port of 16020 (http://127.0.0.1:16020/fmi/xml/FMPXMLRESULT.xml?-dbnames). So it’s like XML is enabled on port 443, but not for the Custom Web Publishing port 16020. How is that possible?
       
      For reasons we don’t fully understand and haven’t figure out how to correct, both the FileMaker Master and the Worker machines ended up with the Web Publishing Engine. So I tried the port 16020 request on the Master server, and it works! Which is great, except we want it to work on the Worker machine, not the Database server which ended up with a WPE.
       
      Some questions:
      1)      We know XML is enabled on the main (port 443) site, what do we need to do to make work on the localhost:16020 site?
      a. I hope this involves moving the ‘Web Server’ listed in the Admin Console to the Worker machine, but if not any info on what might be going on there would be great.
      2)      If we can’t get the Worker machine to realize XML is enabled on port 16020, can we change the FM config so Zulu doesn’t use port 16020 ‘for direct WPE address.’?
      3)      If we can’t do that, are there any issues with installing it on the Master, other than the obvious issue that we don’t want the WPE on that machine?
      Thanks for any insight anyone might have.
    • By ddinisco
      Using the script step export field contents, I can not export the contents of a container field. Error message reads ...could not be created on this disk. use a different name, make more room on the disk or use a different disk. I know I have had this in years past, but I can not remember the fix for this. I found something about setting the fonts to .ttf, but I am on a mac running fmpa16. Any help would be much appreciated.
      David
    • By fmdataweb
      I'm doing an export of a table with 5 fields to an Excel file with an XSL stylesheet to control the formatting of the Excel data. So far it's working well - I just need to add some additional formatting for a few of the cells. I'm looking for help with examples/syntax for setting the following attributes:
      - making a cell bold
      - changing the font size of a cell
      - making all columns set to auto resize so they fit the contents of each column (same as double clicking the divider between 2 columns)
      All fields I'm exporting are text fields.
      Thanks,
      Steve
×

Important Information

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