Publish/Version history for forms in Dynamics CRM 2011 - dynamics-crm-2011

Is there any way to determine which user and when that last changed or published a form in Dynamics CRM 2011?
I've looked everywhere that I can think of, from the form itself to auditing, customizations in the default solution, system settings and I can't find anything anywhere.
If it isn't turned on by default, how do I turn on auditing on the framework itself instead of the content so we can know next time something strange happens?

There isn't a built-in log or audit for the customization changes.
You can try to build your own with plugins attached to the Publish and PublishAll messages

Related

Source from which dynamic CRM 2011 data is edited

In CRM 2011, a CRM user modified a contact information. I can check that through audit logs the changes that the user made.
Now the user modified the First Name and Last Name of the Contact (required fields in CRM) to blank. Now I know that this is not possible through CRM form as the fields are required in the form.
Also there is no JS or any other code written on the form that can disable that required functionality.
I want to know from where these records have been modified in MS CRM.
Also tracing is been disabled in CRM so we do not have logs for this edit :-(
Any help in this regards will be really helpful.
These fields do not need to be updated on a CRM form directly. They can be updated in various ways. Common suspects are:
Custom plugins
Workflows
External parts accessing the Organization.svc or OrganizationData.svc endpoints
In all scenerio's the Business Required constraint is bypassed. In CRM plugins and workflows can actually act on behalf of the user and doing so it appears as if the user modified affected records himself directly.

Pulling CRM 2011 data into Sharepoint 2013 using a webpart?

I've been hunting all day trying to find some good examples/tutorials on how to pull data into Sharepoint 2013 from CRM 2011. The best thing I have found so far is a SP2010 example, but with VS2012 and SP2013 it seems like so much has changed, and trying to make that tutorial work isn't going well thus far.
I have no experience with SP; with CRM I have used the CrmSvcUtil.exe in the past to generate a class and use that within a .NET app in order to view/update data in CRM. I tried implementing this into my Visual Web Part, but I need to be able to add connection strings to the config file which it doesn't seem are recognized by the web part. I see that I can add a service reference to the CRM Organization service but I'm not sure if/how I can use that to query data. Any help is appreciated, or if anyone could point me in the direction of some good documentation. Thanks!
You have got couple of options.
(1) Use SharePoint 2013 client API.
Consume the client API from your CRM plugin / custom workflow to update the crm data to SharePoint 2013.
(2) Consume SharePoint 2013 webservices from CRM plugin / custom workflow.
I don't think this works in sandbox based solution.

How do I safely add an attribute to an Opportunity?

I am building a plugin that utilizes the new Business Process Flow in Dynamics 2013, and in order to take full advantage of the easy to use check-list style menu I have added two new attributes to the default Opportunity entity in Dynamics CRM.
I have done this in the plugin's customizations.xml file by adding the attributes to the Opportunity Entity under the EntityInfo->Entity->Attributes section of the Entity xml.
The addition of this field to the Opportunity works just as expected, though I am running into issues when uninstalling the plugin.
Since this plugin will be widely available, I can't expect users to keep it on their systems forever.
On uninstallation of the plugin, however, Opportunities can no longer be viewed in the CRM 2013 Online. When I try to view one I get the following:
Critical
Query Builder Error
The specified field does not exist in Microsoft Dynamics CRM
Is there something I can do within the customizations.xml file to ensure that once the plugin solution has been uninstalled, Dynamics CRM will no longer reference these fields?
note: This issue occurs on a brand new instance of Dynamics CRM 2013 (trial) with the plugin simply installed / uninstalled, so no other customizations are linking to changes from the plugin and causing the crash
If you were to make this change via the UI, it would block you from deleting these fields until all dependencies have been removed as well. Because you chose to do this without the assistance of the UI, it is breaking on you. If you go back and make this change via the UI, the customizations.xml file should be properly updated and you should be good to go (or it will error and say where there is still a dependency - making it easy to go and fix it).

Dynamics CRM 2011 ribbon on custom html form

I have a custom asp.net website wich is called from Dynamics CRM 2011 and I need it to look exactly like CRM 2011 standart window.
I managed to create almost all custom webcontrols which look like they are from Dynamics CRM 2011 except one, the Ribbon.
I triedto take out and clean the HTML from CRM but results aren't very good so far.
Does anyone have any ideas?
I'm not sure what else you can do Grigory - copying the existing HTML would only ever have been a head start anyway I would imagine. These are not especially complex looking objects (some divs with background images and rollover effect). Can't you just hand craft it?
There's no way to reuse the native controls and I'm not aware of anything commercial that you can go out and just buy.

How to redirect incompatible clients to mobile version of Microsoft Dynamics CRM 2011?

I want simplify access to Dynamics CRM 2011 by redirecting users to mobile version if they open CRM link in browser that is not a compatible client. Looks like there is no out of the box solution.
You might be able to write an HTTP Module that would do this. It obviously isn't a "supported" customization but should be easy to remove if it causes problems.
The other option is to wait for the Q4 update that is supposed to add multi-browser support.

Resources