Jump to content

CWP/XML Problem with records not found


Marek P
 Share

This topic is 5570 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hi,

I've been experiencing what seems to be erratic behavior using XML urls to get data from a FM database using FileMaker Server 8 Advanced.

While a url like this (formatted here for readability) returns some records:

http://account:[email protected]:80/fmi/xml/FMPXMLRESULT.xml.?

-db=database.fp7&

-lay=layout1&

fieldTwo=xyz&

-find

If I replace it with something like this below, it no longer finds any records, even though fieldOne is a text field containing 1, for every record in the database, and it's present on the layout, and it's also from the same table as the layout context table. (Also, I can see this field in the results of the above query, so I know it's there.)

http://account:[email protected]:80/fmi/xml/FMPXMLRESULT.xml.?

-db=database.fp7&

-lay=layout1&

fieldOne=1&

-find

The message I get is Error Code 401, which is "No records match this request".

Here's the weird thing. If I restart FileMaker Server, the problem goes away, and I get the expected results... at least for a while.

More details:

Everything is running on the same machine: WPE, FMServer, Browser.

FM Server version 8.0v2

WPE version: 8.0.1.28

I am using FM's Accounts and Privileges to restrict access to the table (which the layout is based on), though I don't see how that could be the problem.

Thanks,

Marek

Edited by Guest
I fixed a transcription error, by removing the dash before the field name.
Link to comment
Share on other sites

Martin,

Thanks for the suggestion.

It didn't change anything.

For the record, I went into "Define Database", turned indexing off for "fieldOne" (unchecked "Automatically create indexes as needed", it was already set to "None"), got out of "Define Database", then back in, to change the indexing by checking "Automatically create indexes as needed".

I also restarted FM Server, before retrying and getting the same problem.

Marek

Link to comment
Share on other sites

  • 2 weeks later...
  • 4 months later...

FYI: this problem was resolved in a later version of FM Server or the Web Publishing Engine.

I don't know which component contains the fix, but the problem was resolved by these versions (or possibly before):)

FM Server version 8.0v4

WPE version: 8.0.4.36

-Marek

Link to comment
Share on other sites

This topic is 5570 days old. Please don't post here. Open a new topic instead.

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
 Share

×
×
  • Create New...

Important Information

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