Видео

Ah yes, "underneath the hood" Microsoft purchased what is now the power platform/power apps/dynamics from a company in ~2005 and the legacy defaults are still in place. One reason for this is legacy customizations and solutions my have set/hard coded values from long ago and it is best to preserve these values. However you can override them without any worry if it is a custom field you are creating and not an existing system field or from a 3rd party solutions. In other words, if you are creating the column then feel free to set them as you wish, if you are editing/enhancing someone else's column, use the default values set by the user interface to avoid conflicts.

@@PowerTipps thanks for your respons ^^ It's juste like i thought.

Thanks! I am working on rebooting this channel so more videos should start to come very soon!

Excellent, If there is any other area of the power platform you would like information on let me know! I am working to relaunch this channel and more videos should be arriving soon.

This is hard to answer without more details, Lets say you wanted to have a view of sales orders but only the sales orders which have a total greater than the current monthly average. In this situation I would probably use either Power BI and embed a more advanced report in the app(s) or leverage something like power automate cloud flows (scheduled) in conjunction with a custom field on the sales order which could be used to aggregate your view. This seems like an interesting video topic I may create some content soon explaining these paradigms. (I am relaunching this channel)

They are on the list. Working to relaunch this channel very soon.

maybe this is his baseline excited voice

Absolutely.

No problem, I will be uploading some new content very soon. Thanks for the kind words.

Will do. I will start making more videos again soon! Anything particular regarding plugins that you are interested?

Jimmy Briggs D365 please do, they’re super helpful!

Your best bet will probably be to create two separate forms and control them with security role access. You can limit which users can access which forms by grouping them with security roles. It sounds like your challenge contains users that may be able to be split into roles. Another option with business rules is to use something like a two option set field "field A" make this hidden by default and on the form. When the first user completes their "half" this two option set field can be controlled to appear and be required by business rules. When "field A" has a value of true/yes then you can control the other half of the form to appear with another rule/condition. Two forms will probably be a more elegant solution but it all depends on your stakeholders/customers needs.

You can create an optionset automatically as long as it is not global using the data import feature. You may be able to use a utility like the xrmToolKit to extract the values from the previous admin. You cannot create global optionsets with this method. I see this is an old comment, sorry I was not available to respond in time.

I will be uploading content regularly very soon. Almost all will have the new Unified Interface and I will be walking through changes/comparisons with PowerApps vs Dynamics and the common data service.

instablaster.

Thank you! If there are any specific topics you want to see or would like to help me by suggesting it would be wonderful Omnia!

I have not done that one yet but I will reproduce it in the next couple days and get back to you/make a video.

Yes, I only receive this error when the case I am trying to open had the optionset choice which was deleted. In my test I removed facebook (2483) and cases with this choice produce the error you reference. What is more troubling is that the global option set cannot be updated with the value I removed.