Contents
How to make a field non-editable after creation?
You can create a validation rule using ISCHANGED to prevent changes to certain fields. Here’s an example with Opportunity Name. . Gerat! I will try this out.
How does editorfor datetime work with Stack Overflow?
DataFormatString MUST be EXACT like this ” {0:yyyy-MM-dd}” then and only then @Html.EditorFor works with date picker control. Thanks for contributing an answer to Stack Overflow!
How to prevent editing record in Salesforce Stack Exchange?
Create a new checkbox “Record Locked”. Create a workflow that sets the checkbox to true once the level is “Archived” or “Closed”. Optionally, you’d want to also uncheck this when the level changes again to another value. Prevent making any changes when Level equals Archived or Closed unless User is a Sys Admin.
When to use the Validation rule on the picklist?
This validation rule is on the opportunity object, and what I want to achieve is, if the picklist Level__c is either set to Archived or Closed, the opportunity record can only be edited by the System Administrator. For some reason though, the validation rule also triggers, when I want to set the Level__c to Archived or Closed.
How to create custom fields in project web app?
To create or edit Enterprise Custom Fields On the Project Web App home page, on the Settings menu, click Project Web App Settings. On the Project Web App Server Settings page, click Enterprise Custom fields and Lookup Tables. In the Enterprise Custom Fields section, click the field that you want to edit, or click New Field to create a new field.
How to create custom fields in Enterprise Server?
In the Enterprise Custom Fields section, click the field that you want to edit, or click New Field to create a new field. Fill out the Custom Field page by specifying the custom field options that you want to use.
Can you add custom fields to a user profile?
Similar to adding custom fields to tickets, you can add custom fields to user profiles to store additional customer details. Any custom user fields you create apply to all users. Admins and agents with permissions can create custom user fields. Custom user fields are visible to all agents and are editable by agents with access to all tickets.