Databases
StackOverflow2013
Postsdbo
POUsing AutoMapper to unflatten a DTO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing AutoMapper to unflatten a DTO
    primarykey
    data
    text
    <p>I've been trying to use AutoMapper to save some time going from my DTOs to my domain objects, but I'm having trouble configuring the map so that it works, and I'm beginning to wonder if AutoMapper might be the wrong tool for the job.</p> <p>Consider this example of domain objects (one entity and one value):</p> <pre><code>public class Person { public string Name { get; set; } public StreetAddress Address { get; set; } } public class StreetAddress { public string Address { get; set; } public string City { get; set; } public string State { get; set; } } </code></pre> <p>My DTO (from a Linq-to-SQL object) is coming out looking roughly like this:</p> <pre><code>public class PersonDTO { public string Name { get; set; } public string Address { get; set; } public string City { get; set; } public string State { get; set; } } </code></pre> <p>I'd like to be able to do this in my repository:</p> <pre><code>return Mapper.Map&lt;PersonDTO, Person&gt;(result); </code></pre> <p>I've tried configuring AutoMapper every way I can figure, but I keep getting the generic <strong>Missing type map configuration or unsupported mapping</strong> error, with no details to tell me where I'm failing.</p> <p>I've tried a number of different configurations, but here are a few:</p> <pre><code>Mapper.CreateMap&lt;PersonDTO, Person&gt;() .ForMember(dest =&gt; dest.Address, opt =&gt; opt.MapFrom(Mapper.Map&lt;Person, Domain.StreetAddress&gt;)); </code></pre> <p>and</p> <pre><code>Mapper.CreateMap&lt;Person, Domain.Person&gt;() .ForMember(dest =&gt; dest.Address.Address1, opt =&gt; opt.MapFrom(src =&gt; src.Address)) .ForMember(dest =&gt; dest.Address.City, opt =&gt; opt.MapFrom(src =&gt; src.City)) .ForMember(dest =&gt; dest.Address.State, opt =&gt; opt.MapFrom(src =&gt; src.State)); </code></pre> <p>I've read that <em>flattening</em> objects with AutoMapper is easy, but <em>unflattening</em> them isn't easy...or even possible. Can anyone tell me whether I'm trying to do the impossible, and if not what I'm doing wrong?</p> <p>Note that my actual objects are a little more complicated, so it's possible I'm leaving out info that is the key to the error...if what I'm doing looks right I can provide more info or start simplifying my objects for testing.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDaniel Schilling
    1. USJosh Anderson
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing AutoMapper to unflatten a DTO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POUsing AutoMapper to unflatten a DTO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUsing AutoMapper to unflatten a DTO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHmmm your second configuration looks sweet (aside from its missing Name) and shouldn't it be <PersonDTO, Domain.Person>? Might pay to check Domain.Person and PersonDTO are correct references to your classes mentioned above
      singulars
      1. POUsing AutoMapper to unflatten a DTO
      1. USScozzard
    2. COrelated: http://stackoverflow.com/questions/8159186/automapper-map-dto-back-to-domain-object-with-child-objects
      singulars
      1. POUsing AutoMapper to unflatten a DTO
      1. USRuben Bartelink
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload