Awesome

Using the SourceGenerator

This document provides a brief overview of how to use the source generator to generate mapper classes for your entity classes.

Step 1: Define Your Entity Classes

First, you need to define your entity classes and decorate them with the CrmEntity and CrmField attributes. These attributes specify the mapping between your entity classes and the corresponding CRM entities.

For example, here is a sample Person class decorated with the CrmEntity and CrmField attributes:

[CrmEntity("person")]
public class Person
{
    [CrmField("personid", Mapping = MappingType.PrimaryId)]
    public Guid PersonId { get; set; }

    [CrmField("firstname")]
    public string? FirstName { get; set; }

    [CrmField("lastname")]
    public string? LastName { get; set; }
}

Step 2: Run the Source Generator

The source generator is executed automatically when you build your project. This will generate the mapper classes for each of your entity classes. The mapper classes implement the IEntityMapper<TEntity> interface and are responsible for mapping between your entity classes and the corresponding CRM entities.

Step 3: Use the Mapper Classes

Once the mapper classes have been generated, you can use them to map between your entity classes and the CRM entities. To do this, you need to create an instance of the appropriate mapper class and call its Map methods.

For example, here is how you might use the PersonMapper class to map between a Person object and a CRM entity:

var person = new Person { PersonId = Guid.NewGuid(), FirstName = "John", LastName = "Doe" };
var mapper = new PersonMapper();
var entity = mapper.Map(person);

You can also use the Map method to map from a CRM entity to a Person object. Here is an example:

var entity = new Entity("person");
entity.Id = Guid.NewGuid();
entity["firstname"] = "Jane";
entity["lastname"] = "Doe";

var mapper = new PersonMapper();
var person = mapper.Map(entity);

Mapping Types

• Basic: This is the default mapping type and is used for simple data types such as strings, integers, and booleans.
• Lookup: This mapping type is used for lookup fields in the CRM entity. A lookup field is a field that references another entity record.
• Money: This mapping type is used for money fields in the CRM entity. A money field is a field that stores currency values.
• Formatted: This mapping type is used for formatted fields in the CRM entity. A formatted field is a field that has a specific format, such as a date or time field.
• Options: This mapping type is used for option set fields in the CRM entity. An option set field is a field that allows the user to select from a predefined set of options.
• MultipleOptions: This mapping type is used for multi-select option set fields in the CRM entity. A multi-select option set field is a field that allows the user to select multiple options from a predefined set of options.
• PrimaryId: This mapping type is used for the primary ID field of the CRM entity. The primary ID field is the unique identifier for the entity record.
• DynamicLookup: Similar to Lookup just without a target, for lookups with multiple targets ('customer' / 'regardingobjectid') the target is specified by sending DynamicsMappingsTargets to the mapping function.
• DynamicLookupTarget: This mapping type is returnung the target of a dynamic lookup such as 'regardingobjectid'.

Define Linked Entities with the CrmLink Attribute

In addition to the CrmEntity and CrmField attributes, you can also use the CrmLink attribute to map linked entities. This attribute allows you to establish relationships between different entities in your CRM.

Here's how you can use it:

[CrmEntity("order")]
public class Order
{
    [CrmField("orderid", Mapping = MappingType.PrimaryId)]
    public Guid OrderId { get; set; }

    [CrmField("totalamount")]
    public decimal? TotalAmount { get; set; }

    [CrmLink("person")]
    public Person Person { get; set; }
}

In the example above, the Order class has a Person property that represents the person associated with the order. The CrmLink attribute is used to specify that this property maps to a linked entity in the CRM.

And that's it! You can now use the source generator to generate mapper classes for your entity classes and easily map between your entity classes and the corresponding CRM entities.

Settings (DynamicsMapperSettings)

• DefaultValueHandling: When this setting is set to 'Ignore', when mapping a model to entity all the default values are ignored.
• Mappers: Let you customize the mapping process by implementing one or more of the mappers.

Mappers Inetfaces

• IBasicMapper
• IFormattedValuesMapper
• IMoneyMapper
• IOptionsetMapper
• IOptionSetValueCollectionMapper
• IPrimaryIdMapper
• ILookupMapper
• IDynamicLookupTargetMapper

** every mapper interface is used for the equivalent mapping type ** the DynamicLookupTarget mapping type is using the ILookupMapper

PartialMappers

FastMappers

• Dynamically maps properties based on attributes and expressions.
• Supports custom expressions for overriding default mappings.
• Ensures only attributes with CRM field definitions (CrmFieldAttribute) are considered for mapping.

Usage

var entity = new Entity("person");
entity.Id = Guid.NewGuid();
entity["firstname"] = "Jane";
entity["lastname"] = "Doe";

var partialMapper = PersonMapper.CreatePartialMapper((e) => new { e.FirstName, e.LastName });
var model = partialMapper.Map(entity);

model.FirstName == "Jane" // true
model.LastName == "Doe" // true

*** The creation of the partial mapper is using runtiem expression compilation. It is best to create the mapper once and use it multiple times. (do not create a mapper for each use. this may cause performance issues)