1 of 1 people found this helpful
Sounds like the portal table's match field is not modifiable. When you use a portal to create a new record, the layout table's match field is copied into the new portal table's match field. If that match field is a calculation field or prohibits modification as a field option, you will get this message.
You'll need to either change how your match field is defined or use a different method for adding the new portal record.
I can add using FMP 15 Advanced. Match record shows key. When using regular FMP 15, I get the not modifiable dialog and the match field is empty.
This does not change my previous reply. Whether the match field is or is not empty is not the issue.
When you check the field type and field auto-enter options in Manage | Database | Fields, what do you find specified for the portal table's match field?
What field type?
The fields are defined as a text and are indexed. The relationship is kCompany Id = kCompany Id with Allow creations of records checked. On the layout all fields are checked for entry in browse mode.
The data type of the portal table's match field is the only one we need to look at. Make sure that it is text--which you've done if that's what you mean by "the fields are defined as text".
And under auto-enter fields options on the match field, is "Prohibit modification" selected?
Please post a minimally sufficient example (a FMP solution) that demonstrates your problem.
This posses a big problem as the file is large live file that is running a business as we speak. I just tried scripting go to last portal row and set the kCompany ID field in the portal to the kCompany ID in the current record. This works in FMP Advanced same as just typing in the last row fields. In FMP 15 the script fails with can’t modify field dialog.
I am using Citrix to access the data file. I have spent most of my day going over security access. The user type Associate works when using Advanced where I can see what’s going on, but when logged in using 15 reg. I get the field not modifiable dialog. The user type has access to the layouts, records and fields to create, modify
, just not delete. I am going nuts with this!
The fact that you are using Citrix should not be an issue. Checking access permissions makes sense as you can get this error if a field is set in the privilege set to not be modifiable for the current user.
I realize that it's a lot, but if you take a clone of a back up copy, possibly after stripping out a lot of layouts that are not applicable, you can upload the clone here for others to examine. If you choose to do that please:
Tell us what layout to look at so that we don't have to guess.
Provide both a full access and a typical use access level account name and password for opening the file that is not externally authenticated. You can pretty easily create two such accounts in the clone that you upload so that you aren't giving out something that can access anything but the copy that you are sharing.
Hope you figure it out soon.
your key filed is set to autoenter as a serial number ir uuid or something?
I get what you are pointing out here and it's definitely a design mistake if it's set up that way, but I don't see how that would trigger the specific error message reported.
Another thing that you might need to do is check every field in the portal's table for anything that would prohibit modification--both in terms of field level access privileges and auto-enter limitations.
Aside from the issue you're trying to resolve, just from a UI approach, you might take a look at this article :
The ability of creating a record in a portal is nice, but once the list gets so long, the user has to know to scroll to the bottom to add a new record. This approach is a nice solution In my opinion. Thanks to Christo and the great folks at Excelisys for the idea.
Thanks. I will show this to my client. It certainly is more elegant than what I came up with.
I have resolved my problem adding a new record to a portal.
Sent from my iPad Pro