Skip to main content

XrmToolBox: AutoNumberUpdater - new StateCode filter

Post a Comment

Dynamics 365 App Designer - Web Interface is going to be / already deprecated?

In version 1710 (9.0.2.2279) of Dynamics 365 Online we get this dialog to create a new app…
As you can see it contains the Client options Web and Unified Interface.

clip_image004

After an automatic minor update to the newer version 1710 (9.1.0.33) online you only have this dialog available.

clip_image002

This version creates a unified interface app by default and you cannot create apps with a web interface anymore.

Microsoft is transitioning from the classic web interface to the relatively new unified interface.

Is this the version where we cannot create new web interface based apps anymore?

Either this is a bug or we face the next wave mentioned in Steve Mordue’s article:

https://stevemordue.com/the-transition-to-unified-interface/

Labels:

Comments

  1. eekOctober 26, 2018 at 10:36 AM

    It’s not a bug. 9.1 has the unified interface for all new apps but still supports the web refresh interface for existing apps.

    10.0 (April 2019) will probably have the unified interface across all platforms.

    ReplyDelete
  2. Andreas CieslikOctober 26, 2018 at 4:22 PM

    It obviously is not and is not only for new trials as its documented here:
    https://blogs.msdn.microsoft.com/crm/2018/10/05/announcing-changes-to-new-trials-and-new-cds-orgs/
    thanks to Gred DeCarlo who brought that up on my LinkedIn post...

    ReplyDelete

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...
16 comments
Read more

Regarding SPFieldMultiLineText (Add HTML/URL content to a field) programmatically

I recently tried so set some HTML content in a SharePoint list column of type SPFieldMultiLineText. My first approach was this piece of code: SPFieldMultiLineText field = item.Fields.GetFieldByInternalName( "Associated Documents" ) as SPFieldMultiLineText; StringBuilder docList = new StringBuilder(); docList.Append( " " ); foreach (DataRow docRow in addDocs) { DataRow[] parent = dr.Table.DataSet.Tables[0].Select( "DOK_ID=" + docRow[ "DOK_MGD_ID" ].ToString()); if (parent != null && parent.Length > 0) { docList.AppendFormat( " {1} " , parent[0][ "FilePath" ].ToString(), parent[0][ "Title" ].ToString()); } } if (docList.Length > 0) { // remove trailing tag docList.Remove(docList.Length-5, 5); } docList.Append( " " ); string newValue = docList.ToString(); item[field.Title] = newValue; What this code does is to get all associated documents to the main document and to add these docu...
1 comment
Read more

CRM 2016 SP1: Solution import failed with Solution With Id = 12ac16ec-41d5-1685-a230-0b1c31499250 Does Not Exist

Importing Solutions with the upgrade solution (holding solution) option is still not stable with CRM 2016 SP1 On-Premise. Ronald Lemmon already posted the same issue on his blog: http://ronaldlemmen.blogspot.de/2015/11/solution-with-id-86ac16ec-41d7-4685.html I expected it to be fixed with SP1 but it is still happening every now and then. With this query and the solution id (guid) of the error message you are able to find records in the ProcessTriggerBase table that reference the guid of a failed import from a holding solution that is not existing in the system anymore. select * from ProcessTriggerBase where solutionid = 'YOUR_SOLUTION_GUID' Due to this reference to a solution id not existing in the system you will not be able to import a new version of the target solution to be updated. What I did and this is probably not a supported solution is to update the guid to the actual target solution that is currently deployed in the system. To find out the id of ...
3 comments
Read more