Bryntum Support Forums

Any new about this problem?

Fixed now!

Hi henrique,

I think there might be a misunderstanding here, the way we support "complex mappings" is by allowing dot notation in the dataSource, not in the field name.

This for example is (currently) not supported:

fields : [
  { name : 'team.name' }
]

But this is:

fields : [
  { name : 'teamName', dataSource : 'team.name' }
]

Hope that helps getting things to work the way you want!

This solves the problem, but not my problem. If this is the only solution, is necessary to create all this calculated fields, in all my models, this will need a lot of work to map all the calculated fields, because I have a lot of models inside another model. We are developing a large and complex system in my company, and this scheme to acesses complex fields, using the data source, will bring a lot of complexity to the system.

So, if doesn't work directly, I will create an override in the implementation to fix this in my source code.

Thanks for the help.

Hi,

Unfortunately I don't see any other option currently, supporting complex field names would require a large refactoring and is not something we are planning on doing at the moment.

Hopefully adding dataSource wont be that much of a burden, since you have to add field definitions anyway.

Good luck!