[Beth Villotti]

?Is there a way to give permission for users to add Notes but not delete them? 

I know the notes are in the RecordLink (2000000068) table, but if I remove delete permission to this table, it causes problems in other areas.  For example, our purchasing department can’t convert a purchase quote into a purchase order and our accountant can’t delete a line from a recurring journal entry.

I want our customer service representatives to be able to add notes to sales orders as they go through the steps of processing the orders.  They all need to be able to pick up the process where another leaves off.  I don’t want them to be able to delete notes once they or another user adds them.  Once the order has been shipped and invoiced we will also be able to look back at these notes when they flow through to the posted sales invoice.?

——————————
Beth Villotti
Reaxis Inc.
McDonald PA
——————————

[Joe Shields]

Hi Beth,

You could have a modification done to the ondelete function of the recordlinks table to not allow users to delete records unless they were in a certain role, or just not at all.

I have done this in the comments table to allow users to only delete records they have made for example.

——————————
Joe Shields
Advanced Media Technologies
——————————
——————————————-

[Sue Barrett]

I’ve been looking for the same functionality.
We use Notes on the G/L Register as a way to approve journal exceptions after posting.
Because this is an audit trail – we really don’t want to be able to delete these notes – but haven’t found how to do this to date.
For example – We want to prevent a user from deleting a G/L Register note – but they do need to remove notifications that have been sent to them by another user.

——————————
ES Barrett
NAV Project Manager
Sudbury
——————————
——————————————-

[Greg Enns]

This is totally possible. I did this with an event subscription, and I even set up rules for specific tables.

Here’s the basics…

LOCAL [EventSubscriber] CheckNoteDeletion(VAR Rec : Record “Record Link”;RunTrigger : Boolean)

 IF Rec.Type = Rec.Type::Link THEN

  EXIT;

ParentRecordID := Rec.”Record ID”;

 IF ParentRecordID.TABLENO IN [110,112,114,6660,120,122,124,6650,5107,5109] THEN

    ERROR(‘Notes may not be deleted from this kind of document.’);

 

We did some additional coding so that notes cannot be deleted from SalesHeader and PurchaseHeader tables. If you want the full code for that, send me a message and I’d be happy to share.

——————————
Greg Enns
ERP Coordinator
Technical Prospects
Kaukauna WI
——————————
——————————————-

[Beth Villotti]

?Thanks for all of your ideas.  Much appreciated.

——————————
Beth Villotti
Controller
Reaxis Inc.
McDonald PA
——————————
——————————————-

[Brian Stenglein]

?Try adding Indirect Delete permissions.

——————————
Brian Stenglein
Clow Stamping Company
Merrifield MN
——————————
——————————————-

[Jonathan Harter]

Great topic…something else along the same lines.  
I am currently on ’13 R2 and don’t have visibility of what notes I have sent to other users.
In other words, is there or will there be a sent history to review?
Thank you
Jonathon

——————————
Jonathan Harter
Marshall Wolf Automation
Purchasing Manager
Algonquin IL
——————————
——————————————-

[Naveen Jain]

Agree with Brian Stenglein. In the permission give user indirect delete permission. This way that user will not be able to directly delete the notes, but any postings or order conversions will still able to process.

——————————
Naveen Jain
Director of IT
Symbex Companies
Santa Fe Springs CA
——————————
——————————————-