Getting Started
What are CRM DynaProcs?
How does it work?
What can I do with CRM DynaProcs?
I want to trial the CRM DynaProcs where can I download
an evaluation?
I want to trial the CRM DynaProcs but don't want any
trial software on our servers - what can I do?
What are the system requirements for running CRM CLR Stored
Procedures?
Does it support multiple languages?
Does it work with Dynamics CRM On-line or an internet facing deployment?
If we are inserting many records will it slow down crm?
Why is it slow when I run it first time?
What happens when I re-publish an entity?
Are the stored procedures generic or entity specific?
Can I update custom entities?
I've downloaded the application, now what
do I do?
Can resell DynaProcs?
For more information visit Getting Started guide that contains screenshots of the management application and SQL
Licensing
Can I deploy on our development and test servers?
How many licenses do I need?
Common Tasks
How do I deploy CRM DynaProcs?
How do I create entity specific stored procedures?
The error returned is not very specific, how do
I get more detailed error message?
How do I create a relationship between
entities?
Security
What are the security implications?
What are CRM DynaProcs?
CLR stored procedures are stored procedures that use the .Net framework. See
here
for details.
CRM DynaProcs call the Microsoft Dynamics CRM web service API to manipulate
data.
The stored procedures ship with a Management application that installs and configures
the application using a simple to use wizard.
Stored procedures can be generated tailored to specific attribues and specific entities
using the management application.
How does it work?
The CRM DynaProcs are deployed to a seperate database to the CRM application.
Typically the database is a staging database where data is landed before processing
into CRM. The stored procedures call the CRM web services to process the data
What can I do with CRM DynaProcs?
- Create
- Read
- Update
- Delete
- FetchXML
- Set State
- Change Owner
- Create Relationship
- Delete Relationship
What are the system requirements for running CRM DynaProcs?
.Net Framework 2.0
A seperate SQL Server 2005/2008 database
Microsoft Dynamics 4.0 Installation with valid licenses.
Does it support multiple languages?
Currently, the CRM DynaProcs use the language of the executing user.
We plan to change this in the future.
Will it work with Dynamics CRM On-line?
No not yet, although we are looking to implement this in the near future.
If we are inserting many records will it slow down the CRM Application?
Yes, any data import application will use the CRM web service to import data.
If this is an issue, then we recommend using a seperate CRM web server to import
the data
Why is it slow when I run it first time?
The CRM DynaProcs fetch the entity meta data and store it to cache so
that future requests are much quicker
What happens when I re-publish an entity?
The metadata cache is retrieved again. Any stored procedures generated
for specific entities may need to be regenerated also.
Are the stored procedures generic or entity specific?
There are several 'base' CRM DynaProcs that are generic
across all entities. Specific stored procedures can be generated from the
Management application
Can I update custom entities?
Yes.
How many licenses do I need?
During the application license verification process the application checks the
number of licenses equals or exceeds the number of CRM licensed users
How do I deploy CRM DynaProcs?
The CRM DynaProcs are deployed through the Management application
profile wizard
How do I create entity specific stored procedures?
The management application contains a wizard that will collect the information
in order to generate the stored procedures for the entity.
How do I create a relationship between entities?
Many-to-many relationships should be created using the CreateRelationship stored
procedure
Can I re-sell DynaProcs?
Yes, please contact us
What are the security implications of using CRM DynaProcs
The CRM DynaProcs MUST run in a different database to the CRM server
database - this is typically a data staging database. The CLR stored procedures
deploy tables, functions and stored procedures (CLR and non CLR) in this staging
database.
The SQL server instance must be configured to
enable CLR Integrations
Database connection strings are encrypted.
The CLR Stored procedures run under the credentials of the SQL Server Service account
or the credentials specified by the user (which must exist as a CRM user)
The CLR stored procedures require external access to call the CRM web service
that you configure. The installation deploys the assemblies using an asymmetric
key and a specific security principal as directed by Microsoft.
|