- when use abp suite to create crud page, final i can't find the angular page,but we i create layed solution ,There is no such problem.
- Steps to reproduce the issue:
16 Answer(s)
-
0
In ABP microservice solutions, ABP Suite does not currently support automatic Angular UI CRUD page generation as it does in layered monolithic solutions. This is a known limitation. When you use ABP Suite in a microservice solution, the generated CRUD UI pages may not appear in the Angular project, while in layered solutions, this works as expected.
This issue has been reported by other users and is on the ABP team's list to address. As a workaround, you can manually implement the Angular UI for your microservice entities or consider developing the CRUD pages in a layered solution and then adapting the code for your microservice architecture.
For more details and community discussion, see:
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.
-
0
How to solve this problem?
-
0
Anyone else can help me to sovle this problem?
-
0
[48949912] said: Anyone else can help me to sovle this problem?
Hi, what's your problem exactly? ABP Suite generates CRUD pages for the Microservice Template. Actually, we even have a full Microservice Development Tutorial, which you can check at https://abp.io/docs/latest/tutorials/microservice?UI=NG&DB=EF
Also, you may need to follow the instructions here: https://github.com/abpframework/abp/issues/20827#issuecomment-2624232973
-
0
[EngincanV] said:
[48949912] said: Anyone else can help me to sovle this problem?
Hi, what's your problem exactly? ABP Suite generates CRUD pages for the Microservice Template. Actually, we even have a full Microservice Development Tutorial, which you can check at https://abp.io/docs/latest/tutorials/microservice?UI=NG&DB=EF
Also, you may need to follow the instructions here: https://github.com/abpframework/abp/issues/20827#issuecomment-2624232973
After Create Angular UI by ABP Suite, it throws this exception:
2025-08-06 20:09:16.985 +08:00 [INF] 9/10 - AngularUiGenerateWithSchematicsCommand started... 2025-08-06 20:09:32.875 +08:00 [INF] Running the Angular Schematics command: node run-schematics.mjs "D:/Work/Program/imcsmsa/apps/angular/.suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-nolayers-pro imcsmsa.OrderingService "D:/Work/Program/imcsmsa/services/ordering/.suite/entities/Book.json" "D:/Work/Program/imcsmsa/apps/angular" 2025-08-06 20:09:39.125 +08:00 [INF] Angular Schematics command failed. D:\Work\Program\imcsmsa\apps\angular.suite\schematics\node_modules\execa\lib\error.js:60 error = new Error(message); ^
Error: Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target imcsmsa.OrderingService --source D:/Work/Program/imcsmsa/services/ordering/.suite/entities/Book.json [1m[31m[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.[39m[22m at makeError (D:\Work\Program\imcsmsa\apps\angular.suite\schematics\node_modules\execa\lib\error.js:60:11) at handlePromise (D:\Work\Program\imcsmsa\apps\angular.suite\schematics\node_modules\execa\index.js:118:26) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async file:///D:/Work/Program/imcsmsa/apps/angular/.suite/schematics/run-schematics.mjs:6:20 { shortMessage: 'Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target imcsmsa.OrderingService --source D:/Work/Program/imcsmsa/services/ordering/.suite/entities/Book.json', command: '.suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target imcsmsa.OrderingService --source D:/Work/Program/imcsmsa/services/ordering/.suite/entities/Book.json', escapedCommand: '".suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" --template app-nolayers-pro --target imcsmsa.OrderingService --source "D:/Work/Program/imcsmsa/services/ordering/.suite/entities/Book.json"', exitCode: 1, signal: undefined, signalDescription: undefined, stdout: '', stderr: '\x1B[1m\x1B[31m[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.\x1B[39m\x1B[22m', failed: true, timedOut: false, isCanceled: false, killed: false }
Node.js v24.4.1
-
0
Hello,
I could not produce the same problem on my end. Can you share the ABP version you have used to create your application along with the suite version?
If you prefer, you can send me a minimal reproducible example. Here is my e-mail address: sumeyye.kurtulus@volosoft.com
Thank you for your cooperation.
-
0
[sumeyye.kurtulus] said: Hello,
I could not produce the same problem on my end. Can you share the ABP version you have used to create your application along with the suite version?
If you prefer, you can send me a minimal reproducible example. Here is my e-mail address: sumeyye.kurtulus@volosoft.com
Thank you for your cooperation.
I have created two different types of solutions separately. ABP Suite Version is 9.2.3. After Create Angular UI by ABP Suite and Create same entity. The Layered Solution is succeed,but The Microservice Solution is failed.
Layered Solution logs: 2025-08-07 11:58:36.807 +08:00 [INF] 10/11 - AngularUiGenerateWithSchematicsCommand started... 2025-08-07 11:58:36.808 +08:00 [INF] Running the Angular Schematics command: node run-schematics.mjs "E:/work/spctest/angular/.suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-pro spctest "E:/work/spctest/.suite/entities/Book.json" "E:/work/spctest/angular" 2025-08-07 11:58:38.979 +08:00 [INF] Angular Schematics command executed successfully. [36mUPDATE[39m src/app/books/book/providers/book-base.routes.ts (294 bytes) [36mUPDATE[39m src/app/books/book/components/book-detail.component.html (2408 bytes) [36mUPDATE[39m src/app/books/book/components/book.abstract.component.ts (1701 bytes) [36mUPDATE[39m src/app/books/book/components/book.component.html (8360 bytes) [36mUPDATE[39m src/app/books/book/services/book-detail.abstract.service.ts (1794 bytes) [36mUPDATE[39m src/app/books/book/services/book.abstract.service.ts (4119 bytes) [36mUPDATE[39m src/app/proxy/generate-proxy.json (38582 bytes) [36mUPDATE[39m src/app/proxy/books/book.service.ts (4106 bytes) [36mUPDATE[39m src/app/proxy/books/models.ts (657 bytes) [36mUPDATE[39m src/app/proxy/shared/models.ts (297 bytes) [36mUPDATE[39m src/app/proxy/books/index.ts (92 bytes) [36mUPDATE[39m src/app/proxy/shared/index.ts (26 bytes) [36mUPDATE[39m src/app/proxy/index.ts (96 bytes)
2025-08-07 11:58:39.121 +08:00 [INF] 10/11 - AngularUiGenerateWithSchematicsCommand completed. | Duration: 2314 ms.
Microservice Solution logs: 2025-08-07 13:46:39.784 +08:00 [INF] 9/10 - AngularUiGenerateWithSchematicsCommand started... 2025-08-07 13:46:39.786 +08:00 [INF] Running the Angular Schematics command: node run-schematics.mjs "E:/work/msatest/apps/angular/.suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-nolayers-pro msatest.OrderingService "E:/work/msatest/services/ordering/.suite/entities/Book.json" "E:/work/msatest/apps/angular" 2025-08-07 13:46:41.545 +08:00 [INF] Angular Schematics command failed. E:\work\msatest\apps\angular.suite\schematics\node_modules\execa\lib\error.js:60 error = new Error(message); ^
Error: Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target msatest.OrderingService --source E:/work/msatest/services/ordering/.suite/entities/Book.json [1m[31m[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.[39m[22m at makeError (E:\work\msatest\apps\angular.suite\schematics\node_modules\execa\lib\error.js:60:11) at handlePromise (E:\work\msatest\apps\angular.suite\schematics\node_modules\execa\index.js:118:26) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async file:///E:/work/msatest/apps/angular/.suite/schematics/run-schematics.mjs:6:20 { shortMessage: 'Command failed with exit code 1: .suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target msatest.OrderingService --source E:/work/msatest/services/ordering/.suite/entities/Book.json', command: '.suite/schematics/node_modules/.bin/ng g .suite/schematics/collection.json:entity --template app-nolayers-pro --target msatest.OrderingService --source E:/work/msatest/services/ordering/.suite/entities/Book.json', escapedCommand: '".suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" --template app-nolayers-pro --target msatest.OrderingService --source "E:/work/msatest/services/ordering/.suite/entities/Book.json"', exitCode: 1, signal: undefined, signalDescription: undefined, stdout: '', stderr: '\x1B[1m\x1B[31m[Project Not Found] A project matching entity solution name or a default project does not exist in your Angular workspace.\x1B[39m\x1B[22m', failed: true, timedOut: false, isCanceled: false, killed: false }
Node.js v24.5.0
2025-08-07 13:46:41.553 +08:00 [INF] 9/10 - AngularUiGenerateWithSchematicsCommand completed. | Duration: 1769 ms.
-
0
Thank you for providing extra details about your problem. However, I still cannot produce it on my end.
Could you share a minimal reproducible example, so that I could assist you further? Here is my e-mail address: sumeyye.kurtulus@volosoft.com
-
0
[sumeyye.kurtulus] said: sumeyye.kurtulus@volosoft.com
I have share a simple example to you!, please check e-mail: sumeyye.kurtulus@volosoft.com
-
0
-
0
I see, could you try sending via google drive or any other cloud provider you prefer?
-
0
[sumeyye.kurtulus] said: I see, could you try sending via google drive or any other cloud provider you prefer?
OK, I have alreay upload example to the cloud , you can down from the link: https://limewire.com/d/fGrED#pRVxOaWo4q
ABP Suite Version : V9.2.3 NodeJS : V24.5.0
-
0
Thank you for sharing a project. I have seen that the related library is missing that will correspond to the order service. I am not sure whether it failed to be generated while creating a service on studio, however you can generate the related library using this command
npx ng g @abp/ng.schematics:create-lib
The name should be
ordering-service
You should sayNo
forIs secondary entrypoint?
You can let me know if you need further assistance. Thank you for your cooperation.
-
0
[sumeyye.kurtulus] said: Thank you for sharing a project. I have seen that the related library is missing that will correspond to the order service. I am not sure whether it failed to be generated while creating a service on studio, however you can generate the related library using this command
npx ng g @abp/ng.schematics:create-lib
The name should be
ordering-service
You should sayNo
forIs secondary entrypoint?
You can let me know if you need further assistance. Thank you for your cooperation.
Excuse me! I Add OrderingService when create microservice solution,
not after create microservice solution.
-
0
[48949912] said:
[sumeyye.kurtulus] said: Thank you for sharing a project. I have seen that the related library is missing that will correspond to the order service. I am not sure whether it failed to be generated while creating a service on studio, however you can generate the related library using this command
npx ng g @abp/ng.schematics:create-lib
The name should be
ordering-service
You should sayNo
forIs secondary entrypoint?
You can let me know if you need further assistance. Thank you for your cooperation.
Excuse me! I Add OrderingService when create microservice solution,
not after create microservice solution.
Excuse me! I found that when I finished create microservice solution ,and then add a custom microservice. after add a custom microservice,then to create angular UI,It‘s succeed. what's the reason?
-
0
I have investigated the reason. However, I cannot produce the same problem on the latest studio version that is 1.1.2.
I suspect that create-lib command would have failed somehow. You could try on this studio version. You can also check your studio ui logs that is under
~/.abp/studio/ui
or%UserProfile%\.abp\studio\ui
depending on your operating system