Large model design

[Adeagbo]

Hi

I am currently working on an ERP system and it involve a large number of tables.
Can somebody help on using openaccess in desgning large entity model.
I want to do a modular design that will allow me to breakup the model into smaller unit in different project
With little replication of code.

Thank you.

[IT-Als]

Hi Adeagbo,

As far as I know the only way to do it at the moment is to use the Fluent Mapping API.

By using the AggregateMetadataSource it is possible to merge metadata from different MetadataSources into one model.
Please check this link for an example.

Regards

Henrik

[Adeagbo]

Thanks Henrik

I think I will have to have a close look at the fluent API.

[Ivailo]

Hi Adeagbo,

Henrik is correct and this is probably the best way to split your model into manageable pieces.

You can also consider using the new Fluent Code Generation we are offering so that you can shorten the process of creating the initial mapping code with Fluent API. You can then delete the Visual Designer rlinq file and you can continue working with classes only (and maintaining them manually), to avoid the slowness of working with large models.

 

Kind regards,
Ivailo
the Telerik team

[IT-Als]

Hi Adeagbo,

If you found the answer useful please mark it as answered so that other visitors of the forum will find their answers easier.

@Ivailo:

Thanks for joining in on the Fluent Code Generation. This will be the absolute best way of doing it.
Once you have you initial model and get used to the Fluent style it is so much easier.

Regards

Henrik

[Adeagbo]

Hi

Thanks for the info, I am current using the fluent API for the implementation of my ERP model.
I believe with the information I gathered from OpenAccess documentation on Fluent API, It should resolved the problem.

thank you.