More Errors in 8.5.0 and also, latest version of the Power Tools fixis some issues but leaves some still in the process with added extra.
ERROR in ./src/app/main/masterData/oraX_BatchNumbers/oraX_BatchNumbers.component.ts
Module not found: Error: Can't resolve '@abp/notify/notify.service' in 'W:\BRM\BRM-Versions\angular\src\app\main\masterData\oraX_BatchNumbers'
ERROR in ./src/app/main/masterData/oraX_CustomerMasters/oraX_CustomerMasters.component.ts
Module not found: Error: Can't resolve '@abp/notify/notify.service' in 'W:\BRM\BRM-Versions\angular\src\app\main\masterData\oraX_CustomerMasters'
ERROR in ./src/app/main/masterData/oraX_BatchNumbers/oraX_BatchNumbers.component.ts
Module not found: Error: Can't resolve 'primeng/components/paginator/paginator' in 'W:\BRM\BRM-Versions\angular\src\app\main\masterData\oraX_BatchNumbers'
ERROR in ./src/app/main/masterData/oraX_CustomerMasters/oraX_CustomerMasters.component.ts
Module not found: Error: Can't resolve 'primeng/components/paginator/paginator' in 'W:\BRM\BRM-Versions\angular\src\app\main\masterData\oraX_CustomerMasters'
ERROR in ./src/app/main/masterData/oraX_BatchNumbers/oraX_BatchNumbers.component.ts
Module not found: Error: Can't resolve 'primeng/components/table/table' in 'W:\BRM\BRM-Versions\angular\src\app\main\masterData\oraX_BatchNumbers'
ERROR in ./src/app/main/masterData/oraX_CustomerMasters/oraX_CustomerMasters.component.ts
Module not found: Error: Can't resolve 'primeng/components/table/table' in 'W:\BRM\BRM-Versions\angular\src\app\main\masterData\oraX_CustomerMasters'
In the new power tools the date for exporting to excels styling is not creating correctly and needs to be manually allocated for each date field in the excel code.
Hi ismcagdas,
Apologies, where on Github should I log this?
Just another thing to add.
After downloading 8.4 today most of the baove has been resolved as Power Tools seems to have been updated on the template.
There are still somet things that are giving issues.
I see that there is now a different package used for it: using BRM.DataExporting.Excel.NPOI; public class UserListExcelExporter : NpoiExcelExporterBase, IUserListExcelExporter
The problem with this is that the existing power tools still generate the files with: using BRM.DataExporting.Excel.EpPlus: public class TransactionDocumentListsExcelExporter : EpPlusExcelExporterBase, ITransactionDocumentListsExcelExporter
It is something that can be fixed as processed manually, just thought I would reference it here to let you guys know about it if not yet known.
i 「wdm」: Compiling... 70% building 152/152 modules 0 active ERROR in src/app/admin/admin.module.ts(8,10): error TS2724: Module '"C:/8.4.0---BRM-License/BRM 8.4.0/angular/node_modules/primeng/primeng"' has no exported member 'DataTableModule'. Did you mean 'TreeTableModule'? src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(10,27): error TS2307: Cannot find module 'primeng/components/datatable/datatable'. src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(55,18): error TS2339: Property 'primengDatatableHelper' does not exist on type 'TransactionDocumentListsComponent'. src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(60,14): error TS2339: Property 'primengDatatableHelper' does not exist on type 'TransactionDocumentListsComponent'. src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(72,18): error TS2339: Property 'primengDatatableHelper' does not exist on type 'TransactionDocumentListsComponent'. src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(73,18): error TS2339: Property 'primengDatatableHelper' does not exist on type 'TransactionDocumentListsComponent'. src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(74,18): error TS2339: Property 'primengDatatableHelper' does not exist on type 'TransactionDocumentListsComponent'. src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(76,18): error TS2339: Property 'primengDatatableHelper' does not exist on type 'TransactionDocumentListsComponent'. src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(77,18): error TS2339: Property 'primengDatatableHelper' does not exist on type 'TransactionDocumentListsComponent'. src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts(78,18): error TS2339: Property 'primengDatatableHelper' does not exist on type 'TransactionDocumentListsComponent'.
Date: 2020-04-03T18:55:01.835Z - Hash: 8bfb30d8bb110e72befc 1098 unchanged chunks chunk {main} main.js, main.js.map (main) 3.11 MB [initial] [rendered] Time: 7664ms
ERROR in ./node_modules/primeng/components/chart/chart.js Module not found: Error: Can't resolve 'chart.js' in 'C:\8.4.0---BRM-License\BRM 8.4.0\angular\node_modules\primeng\components\chart' ERROR in ./src/app/admin/systemSetup/transactionDocumentLists/transactionDocumentLists.component.ts Module not found: Error: Can't resolve 'primeng/components/datatable/datatable' in 'C:\8.4.0---BRM-License\BRM 8.4.0\angular\src\app\admin\systemSetup\transactionDocumentLists' i 「wdm」: Failed to compile.
Hi Yekalkan,
I am also experiencing this issue and it seems that since 8.4 angular/core there has been many old issues popingup with generation:
Errors occuring in both core and angular after the new version was downloaded.
I have regenerated the entity with the power tools after changing the version, no difference in the results.
Perfect! It works, thank you ismcagdas!
Hi,
Any update on this?
I need to start working on this migration quite urgently.
Hi,
I tried that with both "yarn install" and also just "yarn".
Still get the same issue.
If I do this with 8.2.1 I do not experience any issues.
I have sent an email with a link to the project excluding the Node_modules.
Is there any major changes between 8.2.1 and 8.4 relating to the angular project and how it operates?
Hi,
Yes, tried it, same error.
Curious if this is possible yet?
Would be extremely handy if made possible even if it configurations that we need to populate similar to the templates.