Our Suite team will check the Angular proxy issue. !

Hi, I've opened abp suite and then I've created new microservice. I'm sending to images. !

You can download the module source code, There is no git repos, see https://abp.io/docs/latest/suite/

The %%entity-namespace%% and %%microservice-entities-namespace-prefix%% template variables in ABP Suite

In recent ABP Suite versions (including 1.2.2 and ABP 9.3.x), there was a fix to make these namespace

If you want to adjust or review how these are set: - Open the relevant entity's `.json` file in `suite

Hi **@consultant.ahmet.ulusoy**, These values are generated in the internal methods within the suite

I have no other suggestion except recommending that you update your entities one by one with suite.

dont-run-bundling -no-language-management -chat -file-management After we upgrade to 9.3.3 and abp suite

%entity-namespace%% variable in templates and now, we have issues when we update entitites with abp suite

We are reporting that the ABP Studio Suite is generating the incorrect ref.

Also the github links do not reflect what ABP Suite is generating.

public-website --without-cms-kit --sample-crud-page --dont-run-bundling -chat -file-management Using ABP Suite

`abp add-package @volosoft/abp.ng.theme.lepton-x --with-source-code` or you can download it using suite

dashboard as explained here: https://abp.io/docs/latest/suite/source-code You can again let us know

- The error `NG01203: No value accessor for form control name: 'authorId'` in your ABP Suite-generated

- In a one-to-many navigation (e.g., Book → Author), ABP Suite should generate a dropdown for selecting

**References:** - [ABP Book to Author Relation (Suite)](https://abp.io/docs/latest/tutorials/book-store-with-abp-suite

I knew how to fix the code generated by apb suite.

I hope you can fix apb suite so it generates correct code.

I created a one-to-many navigation using the ABP Suite.

UI template: Angular ABI Suite version: 9.3.3 Browser Console Error ERROR RuntimeError: NG01203:

are not present in Blazor Server starter templates, only in Blazor WebApp projects generated by ABP Suite

After creating a new Blazor WebApp from ABP Suite, problems exist with impersonation from SAAS module

Can ABP Suite download previous versions?

solution now will just put us on the latest ABP Version 9.3 https://abp.io/docs/latest/studio/working-with-suite

Remove and re-add the solution in ABP Suite to refresh its internal cache. 7.

For more details and troubleshooting steps, see: - https://abp.io/docs/latest/suite/generating-crud-page

Create new Entity from Suite. 2. Login to Admin application 3.

Version : 9.3.2 UI : Blazor Database : SQL Server Auth server : Separated 1) Create new Entity from Suite

- When you generate a new solution using the ABP CLI or ABP Suite, you can select options to include

Hi, It seems there is cache problem, can you try cleaning all the nuget cache and install abp suite

/update abp cli: ```bash dotnet tool update --global Volo.Abp.Studio.Cli ``` Then try to open `abp suite

` ```bash abp suite ``` --- > ⚠️ Make sure you're logged in ABP CLI or ABP Studio. you can check if

in, use `abp login` command --- Additionally, it is expected that solutions cannot be created on Suite

This prevents ABP Studio from working properly, including project creation and ABP Suite operations.

- In ABP Suite 9.3.x, the Angular UI code generation system was updated to support Angular's new standalone

However, if your project or Suite configuration is not fully aligned with the new structure, UI code

**ABP Suite Compatibility** - ABP Suite 9.3.x generates Angular UI only if the project structure

- Try creating a fresh project with ABP Suite 9.3.2 and compare the Angular folder structure and

**Known Regression** - There is a known regression in ABP Suite 9.3.x affecting Angular UI code

# ABP Suite Angular UI Generation Issue ## Description ABP Suite 9.3.2 is not auto-generating Angular

the same process works perfectly in version 9.2.2. ## Issue Details * **Working Version:** ABP Suite

forms, services) are auto-generated successfully when creating entities * **Broken Version:** ABP Suite

layers generate properly) * **UI Framework:** Angular with LeptonX Lite theme ## Environment * ABP Suite

Create new project with ABP Suite 9.3.2 2. Add entity through Suite interface 3.

ABP Suite 9.3.2 - Angular UI Components Not Auto-Generated

- When you change a property type (e.g., from DateTime to Enum) in an entity generated by ABP Suite,

Delete the old property from the entity in ABP Suite before adding the new enum property. 2.

Re-add the property with the new type (enum) in ABP Suite. 5.

Regenerate the code using ABP Suite. 6.

/suite/generating-entities-from-an-existing-database-table) - [ABP Support: Not able to save changes]

- Downloading via ABP Suite is an alternative, but if Suite is also failing with "An internal error

Additionally, I read somewhere that I can grab source files from ABP Suite, but ABP Suite isn't working

Once the build succeeds, return to ABP Suite and try generating the entity again.

This is a common step in the ABP Suite workflow: the Suite relies on a successful build to generate migrations

Hi, I created entity over suite and then error occur.

Our suite team will check this.

hi Is the build error caused by the Suite? Thanks.

When I create an entity in ABP Suite, I encounter the error shown in the screenshot I attached.

. --- Sources: - [ABP Suite CRUD Generator: startIndex must be non-negative](https://abp.io/support

> [maliming] said: > Great I found another bug： First add a new entity and save/generate by ABP Suite

> [48949912] said: > > [maliming] said: > > I will forward to our suite team. > > > > Thanks.

I will forward to our suite team. Thanks.

> [maliming] said: > I will forward to our suite team. > > Thanks. Excuse me!

- In ABP Suite, when you create a master-detail (master/child) relationship for MongoDB, the generated

- At the same time, the Suite generates a separate repository, Mongo collection, and application service

- As of now, ABP Suite does not automatically synchronize or populate the internal child collection

Sources: - https://abp.io/docs/latest/suite/creating-master-detail-relationship --- _This response was

At the moment, ABP Suite generates the child entity by inheriting from `Entity` (not `AggregateRoot`)

The Suite merges 2 different aproches but just using one.

The code generated by ABP Suite for Create and Update operations already wraps these calls with error

This can be achieved by updating the ABP Suite templates, but ideally, this improvement should be included

For now, you can customize your ABP Suite templates to wrap Delete calls with HandleErrorAsync(), similar

In the code generated by ABP Suite, Create and Update calls include this, but Delete does not.

I can fix this with ABP Suite template customization, but it would be better if this were included in