MS CRM 2011 Relationship Behavior,Cascading Rules online free Tutorial download pdf.

Summary:Ms Dynamics CRM 2013 Relationships Patterns Learning Tutorials.

Dynamics CRM Relationship Behavior:
                     For N:1 and 1:N relationships there are settings for the relationship behavior, also called
cascading rules, which apply to the following operations:

1. Assign
2. Share
3. Unshare
4. Reparent
5. Delete
6. Merge

                              Figure 23.4, the Type of Behavior drop-down contains four options:

• Parental
• Referential
• Referential, Restrict Delete
• Configurable Cascading

         The first three options are templates, and the last option Configurable Cascading allows you to configure the cascading manually for each operation.
          The first four operations, Assign, Share, Unshare, and Reparent, shares these same cascading types:
Cascade All: This option affects the current entity record and its related entity records. So, the operation is performed on both entities.
Cascade Active: This option affects the current entity record and its related entity records that have a status of Active.
 Cascade User-Owned: This option affects the current entity record and its related entity records that are owned by the user who is performing the operation only.
Cascade None:This option affects only the current entity without affecting the related entity records.

The Delete operation has different cascading options as follows:
Cascade All:This option is the same as explained for the other operations with the consideration that if you have a relationship 1:N between Account and Contact and you have one account record with 10 contacts related, when you delete the account, all 10 contacts will be also deleted.
Remove Link:Using the preceding example, if you delete the account record, the contacts won’t be deleted but the link between the contacts to the account will be removed.
Restrict:Using the earlier example, you won’t be able to delete the account until you delete all the related contacts manually first. Only when the account doesn’t have any related records can it be deleted.

The Merge operation will change between Cascade None and Cascade All, depending on the primary entity selected, and can’t be modified.

More Related Articles:
                      Microsoft Dynamics CRM Relationships
                      Dynamics CRM Customizing Entities Tutorial Part-1 Pdf free download 
                      Microsoft Dynamics CRM Customizing Entities Tutorial Part-2 Pdf free download

Relationships in Microsoft Dynamics CRM 2013 free online learning tutorials

Summary:Relationships in ms dynamics crm 2011 online Training Tutorials 
Relationships:
                        Not to be confused with relationships/connections as found on the interface level, relationships on the schema level are programmatic.That being said, relationships are very user-friendly; you don’t need to be a database system administrator expert to use and configure relationships between entities.
Microsoft Dynamics CRM supports the following relationships:

1. 1:N relationships (one to many)
2. N:1 relationships (many to one)
3. N:N relationships (many to many)

    can add as many relationships as you want and can also add more than one relationship to the same entity. Example:
you can have a custom entity called Customer and add two fields called Primary Contact and Secondary Contact-both related to the entity Contacts.Finally, another feature to relationships is the ability to relate an entity to itself, which is referred as self-referential. Using this type of relationship, you can use any type of relationship (1:N, N:1 or N:N) to relate an entity to itself.

1:N Relationships:
Figure 23.3 displays the window where you can create a new 1:N relationship. With this type of relationship, the primary entity is the one you are customizing. For example, if you are working with the Account entity, you could use this type of relationship to specify the primary account for another entity, such as Contacts, for which the custom field defined by this relationship will contain only one account

FIGURE 23.3 Creating a new 1: N relationship.

N:1 Relationships:
           With this type of relationship, the primary entity is the one you select. Therefore, the entity you are customizing is the related entity. For example, if you wanted a Contact to have multiple Accounts associated with it, you would apply this relationship to the Account entity.
 N:N Relationships:
           With this type of relationship, there is not one primary entity and another secondary or related entity because they act as both types. For example, you might want to have one Contact related to many Accounts or one Contact related to many Contacts. In a real situation, you could have a Contact with a new person who works for two companies, and each company might have many Contacts apart from this one.

 More Related Articles:
                     Microsoft Dynamics CRM Relationship Patterns,cascading rules
                     Dynamics CRM Customizing Entities Tutorial Part-1 Pdf free download 
                     Microsoft Dynamics CRM Customizing Entities Tutorial Part-2 Pdf free download

Top most 10 Interview Questions and answers for microsoft dynamics Axpta(AX).

Summary: Interview Questions and answers for ms dynamics Axpta wipro, infosys,IBM,HCL ,Accenture.

1. Major customization on forms, tables (That you have faced)

2. What is cluster installation?

3. Table collections?

4. Steps in creating number sequence?

5. Any module you are good at.

6. Collection classes

7. Tables in inventory

8. If you manipulate anything which layer would it affect?

9. Steps in data migration.

10. How to add a lookup in a form

11. What is temporary table and in which context is it used?

12. What are the components in reports?

13. How many types of classes are there?

14. RunBase framework and runbase classes

15. Development tools

16. Communication tools

17. Difference between auto generated specs and generated design specs

18. Display and edit method.

19. Can you say few best practises in ax.

20. Elements in AOT.

21. Can you have graphical representation of ssrs?

22. Steps for ssrs.

23. Steps in ssas.

24. What is the difference between sql queries and dynamics queries.

25. What is the difference between x++ and c#?

26. Installation steps in ax.

27. Difference between doupdate and updates

28. Different delete actions

29. Active, Passive, Delayed joins

30. What can’t you store in containers

31. Difference between arrays and containers

32. Logic for converting string to uppercase

33. Override methods in tables, forms

34. What is super() used for?

35. What is init method?

36. What are the sequence of methods while running a report?

37. What is EDT?

38. What is JumpRef()?

39. About form/ reports/ tables methods.

40. D.B Abstract and final class.

41. D.B ValidateWrite and write.

42. What is dialoge class.

43. Pack and Unpack method.

44. Number of elements in enum.

45. Architecture of MS dynamics AX.

46. Tell us about AIF(MSMQ).

47. What is perspectives?

48. How to design a form in AX using X++?

49. What is report builder?

50. What is Index, properties in Index and types of Index?

51. Any knowledge about Share Point.

52. Concept of Different Layer in AX.

53. difference between temporary table and container?

54. difference between bound and unbound controls?

55. what are maps and which method we use in maps?

56. classes in AIF?

57. how to create runtime query?

58. difference between pass by reference and pass by value?

59. types of relations(normal,field fixed,related field fixed)?

60. what are delete actions?

61. how to access tables of different companies(crosscompany)?

62. What is optimistic concurrency control?

63. What are transactions?

64. how to lock a transactions?

65. what are macros?

66. what is the default link type property?

67. difference between validate write and validate field?

68. Do we have validate write and validate field in form level?

69. what are the methods required for posting a purchase order?

70. how to give null in select query?

For Similar InterView Questions :Click Here

What's new for developers in Ms CRM 2013 and New Features

Summary: Ms crm 2013 new features and advantages for developers.

Microsoft Dynamics CRM 2013 and Dynamics CRM Online unlock new opportunities and provide a single development environment for cloud-based and on-premises deployments. Partners, including independent software vendors, global system integrators, and value-added resellers, can quickly create, package, and distribute Microsoft Dynamics CRM extensions and custom solutions. new features in crm.

Entity images:
         Certain system entities and all custom entities can be enabled to display images in the application. People using the web application can upload images for entity records.

Access teams:
       The Access Team is a new type of the team that doesn’t own records, but, has access to records. Unlike with owner teams, you can create any number of access teams to work on the same records and have team members with different levels of access rights to the record.

Business process flow:
        The Business Process Flow is a new type of the process (workflow) for creating visualizations to guide users through various phases of business processes. Each phase can contain a number of logical steps that have to be completed before a user can move to the next phase. You can customize the business process flow by adding or removing steps, changing the order phases, or adding new entities to the process flow. More information: Model business process flows, and Enable Entity Capabilities.

Real-time workflows:
           The existing workflow execution model that supports asynchronous workflows has been extended to support real-time (synchronous) workflows. Real-time workflows are not queued, as was the case with asynchronous workflows, but execute immediately on-demand or in response to a message being processed by the execution pipeline. Real-time workflows can optionally participate in the database transaction and perform similar functionality to plug-ins, yet can be created by the end user through the web application workflow designer. Developers can create real-time workflow through code. In addition, real-time workflows provide the core processing functionality of actions.

Custom actions:
             Developers can extend the functionality of the standard Microsoft Dynamics CRM system by creating custom messages, with associated request/response classes, known as actions. These actions are available to business applications through web service calls. Typical use of actions is to add new functionality to organization web service or to combine multiple organization web service message requests into a single request.

Mobile and rich client development:
             The OData service endpoint has been enhanced with the addition of authentication support for external mobile and rich client applications. Previously, the OData service endpoint supported only pre-authorized client (script) code provided in web resources. Once an authentication token has been obtained from the OData endpoint, client applications can use that token when sending SOAP based requests to the web services. For more information about the new authentication capability, see Authenticate the user with the web services. For information about mobile application development, see Write mobile and modern apps.

Data encryption:
              Field level data encryption provides higher security for sensitive data, for example passwords stored in an entity record of Microsoft Dynamics CRM. For more information, see Field-level data encryption.

Solution version compatibility changes:
           Starting with this release, solutions exported from a newer version of Microsoft Dynamics CRM cannot be installed into older versions. This includes major/minor version differences.

Asynchronous solution import:
           The new ExecuteAsyncRequest message supports importing solutions, which is a long running operation, as an asynchronous process. This enables improved interactivity for users that are working in an organization during the same time that a solution is being imported.

Quick start for developers:
            New documentation has been added that provides an easier and faster learning experience for developers or non-developers new to Microsoft Dynamics CRM technologies. For more information see Quick start to managed code application development.

Read-optimized forms removed:
Read-optimized forms were a feature that allowed for forms that were optimized for consumption of data. For more information, see the Read-Optimized Forms topic in the in the Microsoft Dynamics CRM 2011 SDK.

Duplicate detection not supported during record create and update in forms :
         Duplicate detection during create and update using the new forms is not included for entities with the updated user interface. Duplicate detection of individual records won’t be supported for custom entities as well. However, to detect duplicates in bulk, you can use the BulkDetectDuplicatesRequest message and the RetrieveDuplicatesRequest message.

Phone number formatting for String attributes:
           String attributes can be formatted to allow click-to-call using Lync or Skype. Adding this capability required the addition of a new FormatName property to the StringAttributeMetadata class and the addition of a StringFormatName class containing members to set valid values.

New form programming methods and event:
     There are new form APIs included in this release. More information: New form programming methods and event.

AttributeMetadata.AttributeTypeName replaces AttributeMetadata.AttributeType AttributeMetadata.AttributeType has been deprecated in favor of the new AttributeMetadata.AttributeTypeName property.

 This new property returns members from the AttributeTypeDisplayName class.
This change was necessary to support the new ImageAttributeMetadata class. The AttributeType value for this class will return AttributeTypeCode.Virtual because there is no value in the AttributeTypeCode enumeration to describe this type. Use AttributeMetadata.AttributeTypeName to retrieve values that correctly identify all types of attributes.