One of my layouts does not return records when I perform finds on the web, even though the searches work on the original layout in FileMaker. It always tells me that there are no records that match the requests. Is this a known problem?

After working with IWP for a while, it really seems to me that FileMaker layouts do not really work well on the web. People say that IWP layouts are just like the originals, but too many things work differently or do not work at all.

The finds actually work when I use an administrative account online, but limited access accounts cannot perform the finds online, just in FileMaker. It seems to make no sense that they can see the data but cannot "find" it.

Please check the EXTENDED PRIVILEGE SETS.

You must enable "fmiwp" for each privilege set that requires IWP access. This might account for the difference with FMP access as the "fmapp" privilege is automatically enabled for all privilege sets.

The differences in behaviour are also documented in the IWP publishing guide.

No, IWP access is enabled for all the users. Also, I cannot find anything in the documentation that explains this strange behavior. I guess it must be a bug I should try to work around. Maybe if I re-create the layout it will work; finds work on different layouts, just not in the one.

Pity you didn't mention about the specific layout before.

Possibly damaged layout - re-create it.

OK, it is not just the layout; it seems to be the table. No search on any layout for that table will work for a limited-access user on the web. Let me see if I can figure out what is wrong with the table.

Alright, now it works when I grant the user the ability to modify fields. For some reason they only need this privilege on the web, not in FileMaker. I do not understand that.

I just tested this with a test account which is using a priv set where:

Records: View only in all tables

Layouts: All View Only

Value Lists: All Modifiable

Scripts: All executable only

I dont have an issue with finds.

See, I do not get this. In my case, the find (for just one of the tables, not all of them) would not work unless the fields were modifiable. I turned on "prohibit modification of value during data entry" to prevent users from actually modifying real data, so I think my problems are pretty much fixed here. You just have to keep changing things if the database does not work on the web.

Can you post the exact priv set settings?

I would rather not do that, but I can say that I just narrowed down the specific privilege that was causing the problem. The way I originally had it, the users could only view the records that met a specific criterion that referenced a related field. When I took this requirement away and gave them viewing access to all records, they were able to perform finds. Again, this was only on the web; the same users were able to perform finds in FileMaker before I extended their privileges.

:idunno: