Update requests-ability to lock down already completed fields

Hi everyone,

I actually just realized today that when I have an automation to send an update request and include fields that are already completed, just for clarity, the receiver of the request can actually change the information in those fields.

If I am incorrect in this statement, please let me know what I am doing wrong.

I was actually going to use this with Quality to send update requests to suppliers about corrective actions they need to take, approvals for chargebacks, etc.

The supplier would need some context, such as the non-conforming material #, the date of the request, the corrective action expected, & the amount of the chargeback expected.

I would not want the supplier to be able to change anything on my sheet.

Thanks for your support!

Freda

Find more posts tagged with

Accepted answers

All comments

SteCoxy

If I've understood correctly, you're including the completing fields just for their reference and to give context to what the update request is about?

If so, you can achieve this through locking the according columns and explaining in the body of the update request notification that the supplier just needs to update the empty columns?

FTesseneer

I tried locking down the columns of the completed fields and I was still able to change them.

But, I am wondering if it is because I am admin on this sheet. I am conducting a little test now with someone who isn't even shared to the sheet to see if they can make changes.

I will post results!

FTesseneer

Ok, update! If I lock down the columns, someone who is not an admin or owner of the sheet cannot change those fields that are already completed.

This is good to know.

Thanks for letting me share my learning experience.

Freda

SteCoxy

that's right - only the owner or those with Admin sharing permissions would be able to change such columns. Glad to have helped :-)

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.