You know I’m a sucker for some open source goodness. This time the goodness is from Aiden “President” Kaskela. (Got something to share? Send your wares to jar@crmtipoftheday.com). The Common Data Service (Current Environment) trigger in Power Apps allows you to run your cloud flow when certain fields are updated, but there are two shortcomings: […]
Tip #1043: The Easy Way To Find The Fields Workflows Depend On
If you have a field on a form which is used to trigger a workflow, you probably do not want to mess with it too much. You certainly do not want to be rapidly changing its value or having Dynamics 365 think the value has changed because, for example, a Flow is updating the entity […]
Tip #933: When a field is not a field
Here’s a Dynamics riddle for you: When is a field not a field? Answer: when it is 2 or more fields. Way back in tip 273, we discussed the maximum number of fields you can have in a Dynamics 365 entity. That maximum is for text/string fields. You should be aware that certain types of […]
Tip #453: Tipster guide to calculated fields
It’s Friday, Karl, Friday! That means, instead of our fingers, we let our magnificent voices do the talking. This video explores Dynamics CRM calculated fields feature. It demonstrates how to perform basic field calculations on an entity, how to use some to the date functions available, and how to populate data from other entities. In […]
Tip #407: Some things are irreversible
Truck goes wherever it pleased. For example, US Patent Office. Andrhe “I’ve got 88 in my handle” Margono could not make up his mind, kept adding then deleting attributes and got himself into a pickle: Recently I was migrating some data from my Dev environment to Test environment and I noticed that there are 2 […]
Tip #315: Help! I can’t move my fields around the form
Mitch “Snapshot” Milam to the rescue once again: There may be a time, when working in the Dynamics CRM form editor, that you notice that the form editor will not allow you to move a field from one section to another. Have you ever seen that? It is not a problem with the form editor, […]
Tip #273: Maximum number of fields
Editor note: this tip only applies to Dynamics 365 on premise. Online has a 1,000 field limit per entity. CRM 2011 had a maximum of 1000 fields per entity in Dynamics CRM. CRM 2013 and 2015 have a maximum of 1023 fields per entity. How are you going to use your 23 more fields?
Tip #256: Painless field replacement
You have a field that you wish was a different data type. For example, you have an option set that you wish was a lookup field. Maybe the values in this list change frequently, and you want to have someone who is not a System Administrator be able to add/modify values in the list. But what about […]
Tip #231: Increase the limits of CRM for Tablets
The tablet app for Dynamics CRM includes limits on what can be included on a form in the app: 75 fields 10 Grids 5 Tabs These limitations are there for a reason: mobile devices have lower RAM than a PC browser, so the default limits are there to ensure good form performance. However, sometimes you […]