Records in tables, that belong to a scoped application, are marked as records in Global application

[mpelyanskiy]

Hello, everyone

I've created a scoped application. One of the tables from this application has been modified to be tracked in an update set.

I've pushed this application to my non-production instance. Now, some of the records, that are created in this table, are marked as created in Global application.

How can that be - a table still belongs to a scoped application according to it's name (contains scoped applicaton prefix of x_12345_tableName), but records in it are created in Global application? Is there a way to fix that?

Thank you.

[Chuck Tomasi]

Interesting. I didn't know about that UI action on the form. Thank you. It appears to only be applicable to non-extended tables.

That being said, if you imported the records with the table, then I would look at the update set that contains those records. They are likely defined that way on the source.

Here's a quick test of a theory I have... Use the application picker to set your scope to global. Try creating a record in that table. Save it. What scope is that record in?

[mpelyanskiy]

Chuck,

Just ran your test record creation - it ended up being marked as Global application record, even though it sits in the scoped application table.

I would suggest that your theory of a table being marked in an Update set is true.

Isnt' that odd? I mean if a record is located in a scoped application table, why would it allow to create a record out of table's scope?

But in any ways - thanks for your quick replies. I guess I'll have to figure something out on how to re-create the table without it being tracked in the Update set, and migrate all records to it respectivelly.

[Chuck Tomasi]

You can set a table to allow cross scope access to create, delete, read, and update records from other scopes. Check the application access tab/section in the table definition form. I suspect it is allowing records to be created from all scopes.

[mpelyanskiy]

Chuck,

I have not modified default setting for controls in that table. In my case they look like Gyazo - c477dce1fd8abaff49cfa281fcbb610b.png   , so the expected behaviour I'd say is to prevent records in the table to be created outside the scope of the application.

[Chuck Tomasi · Accepted solution]

Is that from the Customer table in the Notes application? If that's the case, then I too am curious how those records are able to be created from the Global scope. It looks like it is doing the proper thing in not allowing you to modify them unless you are in the same scope they were created, but how they are being created, I don't know. I haven't use the "Track in Update Set" feature in a scoped app yet so I have no background information to draw upon.