Forum Discussion
Set Unique value based on the (CreatedDate & CreatedBy)
but this will not prevent users from modifying the list through the api or using their own power apps
Hello,
Yes it will :)
Because to access the content type, you have to know the ID.
The ID should not be accessible for the regular end-users.
but what custom content type have to do with this? i mean any list will have a default list content type. so you mean the default list content type id is exposed to end users unlike custom content types ids? by the way i always create site content types and add the columns there, but never thought that using custom content type will provide a secure way to prevent modifying the list using API
Exactly,
If you try to create a list item, either through the interface or API, it will default try to create an object with the content type "Item". However, if you are only working with a custom content type, then the users will never be able to "guess" the content type ID and actually create a real item.
You can look at it this way: if they try to go the wrong way, you will notice it as spam.
The idea is not to remove the default content type. It has to coexist with the custom content type. Just make it hidden on the +new button and make sure content type is not shown as an editable field anywhere.
Yours sincerely,
Aref HalmstrandPlease mark as resolved if this was helpful 🙂
Feel free to like this post 🤩