-
Notifications
You must be signed in to change notification settings - Fork 32
LC0068
Whenever the code performs data access, the containing object should include the Permissions
property to allow the user to run the code with indirect permissions.
This is especially important when the table access is restricted to indirect access trough the users license. For example indirect write on ledger entry tables, or indirect read on the table Sent Emails
For procedure calls the following statements will raise this info:
// Insert
MyTable.Insert();
// Modify
MyTable.Modify();
MyTable.Rename();
// Read
MyTable.Find();
MyTable.FindFirst();
MyTable.FindLast();
MyTable.FindSet();
MyTable.IsEmpty();
// Delete
MyTable.Delete();
MyTable.DeleteAll();
On Reports and Queries each dataitem as to have read permissions
On XmlPorts, depending on the Direction
property, each dataitem needs to have permissions to do read, insert or modifies.
If the current procedure, or the targeting table has the appropriate IndirectPermissions
set, no info is shown if the current object is missing the permissions.
Extension objects do not support the Permission
property.
If you get this diagnostic on an extension object, that means that you will need to move that code to another object, like a codeunit in order to comply with this rule.
Also check https://github.com/StefanMaron/BusinessCentral.LinterCop/issues/763