I am following the Connector for Microsoft Dynamics Installation Guide to setup a connection between Dynamics CRM and AX. I am asked to Open the object configuration file.
Where are these object configuration files located?
There is one generated .config file per entity in CRM that you have selected for integration.
These object configuration files can be found in:
%PROGRAMFILES(x86)%\Microsoft Dynamics\Microsoft Dynamics
Adapter\Adapters\Microsoft.Dynamics.Integration.Adapters.Crm2011\ObjectConfig\your organization name
Related
I've created a new (and my first) report in Dynamics 365 using the built-in wizard, and now I want to modify it to join more entities and add columns from them.
Modifying and testing the FetchXML was not an issue using XrmToolbox. I was able to connect, verify my XML and retrieve the expected columns.
Next, I followed some instructions online and installed the Microsoft Dynamics CRM Report Authoring Tools, downloaded the RDL, opened Visual Studio, created an empty Report Server project and added the RDL to my project.
And this is where my problems begin...
While attempting to modify the FetchXML in the DSMain dataset in the RDL, I encounter the error "The selected data extension MSCRMFETCH is not installed or cannot be loaded."
I thought the Microsoft Dynamics CRM Report Authoring Tools would have included this extension.
What am I doing wrong?
I have created a custom document library using Visual Studio in Sharepoint 2010. When i deploy the docusign it is available on other Document libraries that was created directly on site but is not available with the custom form i have created using the Visual Studio. The Docusign connector is also not available with the "Permissions and Management" in the Library settings of the custom form but is available with the other document library settings.
Any ideas ?
thanks in advance.
The installer script will install the DocuSign Sharepoint connector for any SPList of BaseType == SPBaseType.DocumentLibrary (1) and the Hidden property == false.
I'm building a Lightswitch application using MS Visual Studio 2013. As part of this I access data through an OData url (referencing a dynamics nav project) which does not seem to want to pick up the company data in the url. (It does without it). However then within Visual Studio I only see the column headers and no data. When I debug I get the following error message:
"Cannot process the request because the default Microsoft Dynamics NAV company cannot be found. You can specify a default company in the service configuration file, or specify one for each tenant, or you can add a query string in the form of "company=[name]". You can see the available companies by accessing the default OData web service, Company. For more information, see "OData Web Services" in Help."
For example: (OData url):
localhost:7048/DynamicsNAV70/OData/Company('CRONUS%20International%20Ltd.')/SalesOrder
But only viewable as:
localhost:7048/DynamicsNAV70/OData/ and then selecting SalesOrder
My question is, what config files are they refering to? (Visual studio?If so how do I add the company name?) "OData Web Services" in Help was of no use.
I had to add additional code within Visual Studio to reference the company, for example:
ServiceReference1.NAV nav = new ServiceReference1.NAV(new Uri("http:...../OData/Company('company_name')/"));
nav.Credentials = new System.Net.NetworkCredential("user", "password", "domain");
Tech Friends,
I could not add MSCRM 2011 WCF service reference in Visual Studio 2010. It throws error when try performing this action. How do we add this service as service reference in Visual Studio 2010 and generate all proxy classes?
Have you tried following these instrutions? Download the Endpoints Using the Dynamics CRM Developer Resources Page.
Specifically in the "Using the WSDL" section.
To add a service reference for these services to a Microsoft Visual
Studio 2010 project, you must append ?WSDL to the service URL when
specifying the address in the Add Service Reference dialog box. For
example, the discovery service WSDL address is
http://servername/xrmservices/2011/discovery.svc?wsdl.
I found the resolution for the problem and I have tested it :)
To add discovery service and organization service as reference in Visual Studio we have to add query strings: ?wsdl=wsdl0
eg:-
.api.crm4.dynamics.com/XRMServices/2011/Organization.svc?wsdl=wsdl0
The same applies for discovery service also.
Check this link:
http://social.msdn.microsoft.com/Forums/en-US/crmdevelopment/thread/033f9831-5e88-4b85-a4eb-a55985f39997
So I've gotten this error message from time to time since working with MS CRM.
System.IO.FileNotFoundException: Microsoft Dynamics CRM has
experienced an error. Reference number for administrators or support: #C0916659
Since there are multiple places for DLLs to live it makes it a pain to maintain.
Here's what I know of so far.
CRM SERVER
c:\Program Files\Microsoft Dynamics CRM\Server\bin - ?
c:\Program Files\Microsoft Dynamics CRM\Server\bin\Assembly - Plugins
c:\Program Files\Microsoft Dynamics CRM\Server\CRMWeb\bin - Supporting DLLs for plugins
ASYNC SERVER
c:\Program Files\Microsoft Dynamics CRM\Server\bin\Assembly - Async workflows and plugins
What else am I missing or need to be corrected on how these paths work and their intended purpose.
Best practice is to register the assemblies to the database.
Plug-ins not-registered in the sandbox can be stored in the Microsoft
Dynamics CRM server's database or the on-disk file system. We strongly
recommend that you store your production-ready plug-ins in the
Microsoft Dynamics CRM database, instead of on-disk. Plug-ins stored
in the database are automatically distributed across multiple
Microsoft Dynamics CRM servers in a data center cluster. On-disk
storage of plug-ins is useful for debugging plug-ins using Microsoft
Visual Studio but is mostly provided for backward compatibility with
callouts. You can debug a plug-in that is stored in the database.
Plug-ins registered in the sandbox must be stored in the database
regardless of the Microsoft Dynamics CRM deployment (on-premises,
IFD/SPLA, or Online).
This excerpt from the MSDN describes the registration possibilities and the paths.
For on-premises or Internet-facing Microsoft Dynamics CRM
installations, when you deploy plug-ins from another computer to the
Microsoft Dynamics CRM server disk (on-disk deployment), the plug-in
assembly must be manually copied to the server before registration.
The assembly must be deployed to the \Program
Files\Microsoft CRM\server\bin\assembly folder on each server where
the plug-in is to execute.
Plug-in registration should be done after the assembly has been copied
to the …\bin\assembly folder on the server to prevent the situation
where a system user causes an event in Microsoft Dynamics CRM to be
raised but the registered plug-in assembly does not yet exist on the
server. For server database deployment, the plug-in assembly is
automatically copied during plug-in registration so that the earlier
situation is not an issue.
Depending on your plug-in’s design, your plug-ins may require other
referenced assemblies to run. Regardless of whether you deploy your
plug-in to the database or disk, if your plug-in requires other
assemblies to run, you must put copies of these assemblies in the
Global Assembly Cache (GAC) on each server where the plug-in is to
execute. This does not apply to a Microsoft Dynamics CRM Online server
because you do not have access to the GAC on that server.
See Register and Deploy Plug-ins