{"id":1114,"date":"2014-12-31T13:07:15","date_gmt":"2014-12-31T07:37:15","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=1114"},"modified":"2014-12-31T13:07:15","modified_gmt":"2014-12-31T07:37:15","slug":"a-tip-while-working-with-field-level-security","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2014\/12\/a-tip-while-working-with-field-level-security\/","title":{"rendered":"A Tip while Working with Field Level Security"},"content":{"rendered":"

Recently we came across a situation. We had a workflow in which we used a field which had field level security enabled on it. There was a custom field called \u201cCredit Amount\u201d that existed on the Account and had a field security enabled on it.<\/p>\n

The workflow in which we were using this field checked a condition whether\u00a0the field Credit Amount\u00a0contained value in it. You can see in the below screen that the\u00a0workflow was also set to execute under a logged in user\u2019s context.<\/p>\n

\"Workflow\"<\/a><\/p>\n

Now, the problem was that when the workflow was executed, it was not performing its operations. Since the Credit Amount field was\u00a0a secured field and the user who was running this workflow did not have the privilege to read the field value, while checking the value of this field condition in workflow,\u00a0it\u00a0always returned NULL even if there was\u00a0an existing value in this field. Due to this the workflow did\u00a0not meet with condition and perform the operations. To overcome this situation, we simply modified the workflow to execute it as the OWNER of the workflow.<\/p>\n

\"Workflow\"<\/a><\/p>\n

So before using fields in the workflow conditions, please check if the field has field security enabled on it or the workflow should run under the user who has appropriate security role.<\/p>\n

Hope this helps!<\/p>\n","protected":false},"excerpt":{"rendered":"

Recently we came across a situation. We had a workflow in which we used a field which had field level security enabled on it. There was a custom field called \u201cCredit Amount\u201d that existed on the Account and had a field security enabled on it. The workflow in which we were using this field checked\u2026 Read More: A Tip while Working with Field Level Security »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,21,22,24,51],"tags":[395,800,1562,1841],"class_list":["post-1114","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm","category-dynamics-crm-2013","category-dynamics-crm-2015","category-dynamics-crm-2016","category-security","tag-crm-2013-dynamics-crm-2013","tag-field","tag-security","tag-workflow"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t