Activities of "johnsonlim"

HI Maliming, Can explain more in details how to do for 2nd options?

Hi Maliming, Thanks. But i have one more question .I find out that under the navigation property tab with "Import entities from ABP module checked", i only able to select entity of Master type but not child type. For my case, i cannot find Department from the list. Can you advise?

Hi Maliming, I have just resend the email to you with the the links to download dll file from we transfer. Can you try?

Hi Maliming, Learn time both dll are of the same. I have email you^^

Hi Maliming, I do have the company entity read in Master Data module and the attribute actually contains company name.Can you advise?

Hi, I successfully create the linkage and able to choose the entity from ABP and my master data module. But then i am not able to click ok button to proceed.Please advise

thanks maliming :)

Yes, i want real navigation property. Please tell me how to do so

Hi All, I have 2 modules in ABP Suites: Master Data Module and Transaction Module . I have all the master data entity and its CRUD page created in Master Data Module. Now i want to create transaction entity, which its attribute requiring reference to the data entity in Master Data Module. i find out that the data entity created in Master Data Module cannot be found in Transaction Module as per the picture.Can you advise what to do? This is the company entity created in Master Data Module.

This is the the page where i want to create data entity and its reference page in Transaction module. i cannot see company entity at all.

[AI-Bot] said:

• Yes, you can lose (have overwritten) your manual EF Core mapping changes if ABP Suite re-generates the same area again. Suite’s “Save and generate” can rewrite generated files (including the DbContext / entity mapping blocks it generated), so a manual change like switching OnDelete(DeleteBehavior.SetNull) to NoAction/Restrict may be reverted on the next generation.

• However, your database foreign key will not disappear by itself just because Suite generates more code. The DB schema only changes when you add/apply a new migration (or drop/recreate/update DB). The main risk is: future generation overwrites your mapping, and then your next migration may try to alter the FK behavior again (or you may start getting migration/update failures again).

What to do to avoid losing it

1. Keep the self-referencing relationship mapping in a place Suite won’t touch, and keep Suite-generated code minimal. Practically:
   • Prefer to configure your self-reference in your own mapping code under OnModelCreating (or the project’s ConfigureYourProjectName() style extension method), not in a file that Suite repeatedly regenerates for the entity.
2. If you must let Suite generate again, be prepared to re-apply the DeleteBehavior fix after generation (and before creating the next migration).
3. Version control is your safety net: after any Suite generation, review the diff and restore your custom mapping if Suite overwrote it.

Sources

• https://abp.io/docs/latest/suite/generating-crud-page
• https://abp.io/docs/latest/solution-templates/layered-web-application/database-configurations
• https://abp.io/community/articles/furp75ex

---

This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

If there is possibilty of code overwritting, shall i proceed?