AXForum  
Вернуться   AXForum > Microsoft Dynamics CRM > Dynamics CRM: Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 18.12.2017, 23:11   #1  
Blog bot is offline
Blog bot
Участник
 
25,475 / 846 (79) +++++++
Регистрация: 28.10.2006
powerobjects: Beginner’s Guide: How to Perform Simple Data Validations on Records
Источник: https://www.powerobjects.com/2017/12...ns-on-records/
==============


Today, we’ll walk users who are relatively new to Microsoft Dynamics 365 through some relatively simple data validation checks.

The Issue


You may come across a scenario where you want to perform a simple verification on a field before you create a record. For example, you may wish to perform a validation to check if the registered Due Date on a record is older than the record’s creation date. Often, validations are implemented with custom code. However, in situations where custom technical work may not be feasible, the solution outlined below can be implemented with ease.

The Solution


Business rules are a potential answer here since a validation can be applied here by comparing the Due Date against the value within the standard ‘Created On’ field. However, this field will not be populated during creation of a record which means Dynamics 365 doesn’t have a value to check against, rendering the sole use of business process flow alone futile.





















A synchronous workflow on the other hand can be triggered to perform this validation before the record is created. The workflow can be stopped with the status of Cancelled if the required criteria is not met. Although this will solve the problem of validating the Due Date field before creating record, the business process error shown by the workflow is less user friendly than the error shown by the business rule.

Also, running synchronous workflows whenever the Due Date field is updated may result in significant processing load which is especially undesirable during peak periods. Therefore, limiting this workflow to only run prior to record creation is ideal while the business rule can be used for validation after record creation.



















To conclude, the synchronous workflow and the business rule can be used in combination to overcome this issue. While the workflow will perform this validation effectively during record creation, the business rule will take over with a much more user-friendly error message once the record is created.

For more Dynamics 365 tips and tricks, be sure to keep checking our blog!

Happy Dynamics 365’ing!



Источник: https://www.powerobjects.com/2017/12...ns-on-records/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
emeadaxsupport: How to perform a data center change (change of the physical location) where a SQL server 2008 R 2 cluster installation and MS Dynamics AX 4.0 is involved? Blog bot DAX Blogs 0 21.06.2014 19:19
emeadaxsupport: SEPA affected objects Blog bot DAX Blogs 0 29.11.2013 13:11
NAV Team: How to: Enable Import/Export of Bank or Payroll Files Using the Data Exchange Framework Blog bot Dynamics CRM: Blogs 0 18.10.2013 02:33
atinkerersnotebook: Using PowerPivot to Analyze Dynamics AX Data Blog bot DAX Blogs 1 05.10.2013 07:23
atinkerersnotebook: Walkthrough & Tutorial Summary Blog bot DAX Blogs 1 09.09.2013 09:11

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 18:31.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.