Difference between CRM Discovery Service and CRM Metadata service?

CRM service - when we need ORG related information like ORG name, Properties, CRM service path for this ORG -- then we use CRM discovery service. This is only to get the ORG related information Metadata service - we use this when we need to interact with the CRM records – create, update or delete anything-- it is very specific to the CRM records. When we need to interact with the CRM entity and attribute - like create an entity (not record) or attribute -- add a value to pick list-- retrieve the pick list value retrieve the entity properties-- attribute property and all we need Meta data service.

Comments

Post a Comment

Hi,

If any one want to give the stagnation and change its most welcome.

Thanks!!
Rajesh Singh.

Popular posts from this blog

Many to Many Relationship in Dynamics CRM 2011.

Image
I get asked about many-to-many (a.k.a. N:N) relationships more than just about any other single topic, so here’s a summary of how they work in Dynamics CRM 2011. I’ll review both “native” and “manual” N:N’s, using a simple Association to Contact relationship to illustrate. This is a classic many-to-many: each association should be able to have multiple contacts associated with it, and each contact should in turn be able to be associated with many associations. Native N:N Relationships With native N:N relationships, you open up an entity for customization, click the N:N relationships link, and click the  New Many to Many Relationship  button and select the entity to create the relationship to. For the Association to Contact N:N relationship, I’ll start from the Association entity: In the previous figure, notice that Do no Display is selected in the Display Option for each side. I only show that to illustrate a point: what this will do is prevent the relationship from be...
Read more

Event Execution Pipeline MSCRM

Image
Pipeline Stages The event pipeline is divided into multiple stages, of which 4 are available to register custom developed or 3rd party plug-ins. Multiple plug-ins that are registered in each stage can be further be ordered (ranked) within that stage during plug-in registration. Event Stage name Stage number Description Pre-Event Pre-validation 10 Stage in the pipeline for plug-ins that are to execute before the main system operation. Plug-ins registered in this stage may execute outside the database transaction. Security Note The pre-validation stage occurs prior to security checks being performed to verify the calling or logged on user has the correct permissions to perform the intended operation. Pre-Event Pre-operation 20 Stage in the pipeline for plug-ins that are to execute before the main system operation. Plug-ins registered in this stage are executed within the database transaction. Platform Core Operation MainOperation 30 In-transacti...
Read more

TRACK OPPORTUNITY SALES STAGE HISTORY

Our Requirement in the business process flow is how we calculate every step time-consuming need to capture and show. Step 1.  First, we can create an  entity to store the BPF stage history and use real-time workflow to create the new entity records. Step 2.  Then create some fields. Add them to the main form. Opportunity – Lookup field Previous- Single line of text field New – Single line of text field From – Date and time field To- Date and time field Duration(hours) – Whole number (Calculated field) Step 3.   Create a calculated field on an entity to calculate the difference between ‘Start Date’ and Now(). Step 4. Create real-time workflow.
Read more