Combining multiple sources into a single output

[David Strickland]

I have a Flat destination class and a complex source containing
multiple child objects
Currently I create multiple maps with the same output type but
different input types.

ie
Mapper.CreateMap(Of destinationType, Source1Type)
Mapper.CreateMap(Of destinationType, Source1Type.SubClass1)
Mapper.CreateMap(Of destinationType, Source1Type.SubClass2)

Then in code I call each sequentially. wrapped in a if not source is
null.

The instantiation of the destination requires all 3 source objects so
I'd like to be able to create 1 map that ensures all 3 are called.

I tried some different options but I typically hit a wall when
SourceType1.Subclass1 == null.

any suggestions

Thanks
Dave

[Jimmy Bogard]

AutoMapper is designed to map a single source object to a single destination object.  If you're trying to do something different, it probably won't work.  Your best bet is to shape the input into a single object.  We've tried looking at this feature, but the problem is that collisions are possible, defeating the purpose.

Thanks,

Jimmy

--
You received this message because you are subscribed to the Google Groups "AutoMapper-users" group.
To post to this group, send email to automapp...@googlegroups.com.
To unsubscribe from this group, send email to automapper-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/automapper-users?hl=en.

[jdsteve...@gmail.com]

So what is the recommended practice for a situation where a ViewModel needs to support a drop down?

AddressViewModel

string Street1

string City

int StateID

List<StateViewModel> AvailableStates

mapped from:

Address

string Street1

string City

int StateID

and a separate call to a repository to get a list of available states? Should I just map the returned States collection to a StateViewModels colelction and then assign the AvailableStates property directly? I just want to be sure there's nothing fluent built in.

[Jimmy Bogard]

Ohhhh good question!

What is the nature of the list of items? Where does it come from?

To unsubscribe from this group and stop receiving emails from it, send an email to automapper-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[jdsteve...@gmail.com]

Well in my case, it comes from a repository that could either be retrieving it from cache or ultimately a local database. It could potentially also be retrieved from a web service by a repository. Here's what I have currently and I really have no complaints with it:

        public static PersonEditVM GetAutoMappedPersonEditVM(Guid personID)

        {

            IMapper mapper = MapperConfig.EntityWebMapper;

            Person person = personID == Guid.Empty ? new Person() : CrmRepository.GetPersonWithContactInfo(personID);

            PersonEditVM vm = mapper.Map<PersonEditVM>(person);

            vm.AvailableStates = mapper.Map<List<StateModel>>(CrmRepository.GetStates())

                                    .OrderBy(s => s.Name)

                                    .ToList();

            vm.AvailablePhoneTypes = mapper.Map<List<PhoneTypeModel>>(CrmRepository.GetPhoneTypes())

                                        .OrderBy(pt => pt.Name)

                                        .ToList();

            return vm;

        }

I'm brand new to AutoMapper...I had my own very basic implementation going and then realized I kept hearing about yours (which looks awesome!)...so apologies if I'm wasting your time on the basics. Thanks for your help!

To unsubscribe from this group and stop receiving emails from it, send an email to automapper-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Powell]

On Tuesday, November 16, 2010 at 1:07:27 PM UTC-5, David Strickland wrote:

I have a Flat destination class and a complex source containing
multiple child objects
Currently I create multiple maps with the same output type but
different input types.

AFAIK, and I could be wrong since 4.2.x, but IMapper.Map<...>(...) supports not only creating the destination object, but also supports operating on an existing instance. So in the case of mapping multiple sources, I would follow that paradigm. I've done that in a couple of places.

Now, mind you, one thing to be cautious of is what to do over collisions if you happen to have overlapping or competing source/destination scenarios. But then, perhaps conditions may work well in your case to decide what/when to allow the mapping to continue.

HTH