Skip to main content

XrmToolBox: AutoNumberUpdater - new StateCode filter

The General Data Protection Regulation (GDPR): Free assessment by Microsoft

The EU’s new General Data Protection Regulation is scheduled to take effect on May 25, 2018. Designed to serve as a uniform set of data protection laws within the EU, it will become law alongside the BDSG in Germany. This means that all affected companies will need to make extensive adjustments to the new legal landscape.

Here are the most important impending changes:

  • Expanded executive responsibility
  • Effective application of data protection law based on increased liability and fines
  • “Privacy by design” and “privacy by default” will become basic principles of data protection law
  • Data Protection Impact Assessments
  • Expanded obligation to report data incidents
  • Expanded documentation regulations (including with regard to information security management systems, or ISMS)
  • Expanded citizens’ rights
  • Modified role for data protection officers

Since there won’t be any transitional period as they take effect, you need to get your company ready for these new laws sooner rather than later.

“The data protection authorities are already preparing to intensify their auditing activities once the GDPR becomes law in May 2018,” warns Thomas Kranig, president of the Bavarian Data Protection Authority.

“Biding your time instead of getting ready for these changes is a very risky move.”

How is your Dynamics 365 environment doing?

Check out the free GDPR assessment tool provided by Microsoft:

https://assessment.microsoft.com/gdpr-compliance

You need help with this whole process to onboard your systems to support the GDPR?

Contact us:
https://www.audius.de/en/it-services/data-protection

Comments

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

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

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