DataTable -> Table Power Tools #8802

AuroraBMS created 4 years ago

Hi Guys,

Does anyone know where this referenced value is defined for the Power Tools generation Angular client side MainTemplate.txt: {DataTable_Import_Here}}{{TurboTable_Import_Here}};

As well as the segment that determines the below needs to be added because it is not there (It is not even part of the primeng package import { TableModule } from 'primeng/primeng';

Basically what is happening is everything relating to TableModule is generated as DataTableModule and this causes a ton of extra work just to fix it after every generation.

@ANZ Team - This might sound a bit rude, but can you please before a release Generate a new application, create a basic table and generate screens, run the application and test if power tools works correctly as this seems to be a regular occurance that something that should not be there is in the powertools app.

# List of issues:

Power Tools - DataTable not referencing TableModule and related primengDatatableHelper which should be primengTableHelper (based on version 8.2.1 Chart.js - This suddenly started making a comeback as an error when starting the template initially - quick fix but annoying if you constantly get a new version of the template from the downloaded zip and start working on it. Main-Module - Table issue with power tools as well. EpExportExcel - for excel being changed to Npoi and not updating the generation for export to export to excel with the correct create sheet paths and removing styling which is generated by the power tools as well for the sheet. ~~Entity Tracking - 8.4 suddenly does not support entity tracking anymore at all~~.** - I see this is in another post.

If the communtiy knows of a quick fix around this that is maybe config in Power Tools that can resolve this it would be greatly appreciated if it can be commented here if it is in the non-user code for Power Tools then I guess we will have to wait for a fix.**

Thanks, Aurora-BMS

19 Answer(s)

0

ismcagdas created 4 years ago
Support Team

Hi @AuroraBMS,

Could you create this issue on GitHub, so we can fix it for the next realase ?

Thanks,
0

AuroraBMS created 4 years ago

Hi ismcagdas,

Apologies, where on Github should I log this?

AuroraBMS created 4 years ago

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.

AuroraBMS created 4 years ago

Some other issues as well:

ERROR in src/app/main/masterData/oraX_CustomerMasters/oraX_CustomerMasters.component.ts:4:31 - error TS2307: Cannot find module '@abp/notify/notify.service'.

4 import { NotifyService } from '@abp/notify/notify.service';
                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/app/main/masterData/oraX_CustomerMasters/oraX_CustomerMasters.component.ts:10:23 - error TS2307: Cannot find module 'primeng/components/table/table'.

10 import { Table } from 'primeng/components/table/table';
                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/app/main/masterData/oraX_CustomerMasters/oraX_CustomerMasters.component.ts:11:27 - error TS2307: Cannot find module 'primeng/components/paginator/paginator'.

11 import { Paginator } from 'primeng/components/paginator/paginator';
                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/app/main/masterData/oraX_CustomerMasters/oraX_CustomerMasters.component.ts:12:31 - error TS2307: Cannot find module 'primeng/components/common/lazyloadevent'.

12 import { LazyLoadEvent } from 'primeng/components/common/lazyloadevent';

0

ismcagdas created 4 years ago
Support Team

Hi @AuroraBMS

We will release a new version soon (in 1-2 hours).

Thank you for reporting this.
0

AuroraBMS created 4 years ago

Hi @Ismcagdas

There are still issues with the following:

ERROR in ./src/app/main/masterData/oraX_ItemMasters/oraX_ItemMasters.component.ts Module not found: Error: Can't resolve '@abp/notify/notify.service' in 'W:\BRM\8.5.0\BRM\angular\src\app\main\masterData\oraX_ItemMasters' ERROR in ./src/app/main/masterData/oraX_ItemMasters/oraX_ItemMasters.component.ts Module not found: Error: Can't resolve 'primeng/components/paginator/paginator' in 'W:\BRM\8.5.0\BRM\angular\src\app\main\masterData\oraX_ItemMasters' ERROR in ./src/app/main/masterData/oraX_ItemMasters/oraX_ItemMasters.component.ts Module not found: Error: Can't resolve 'primeng/components/table/table' in 'W:\BRM\8.5.0\BRM\angular\src\app\main\masterData\oraX_ItemMasters'

I created a custom template for this temporarily as the errors are causing quite a bit of delays.

For those that need to bypass this error replace the below in this folder: Path: \aspnet-core\AspNetZeroRadTool\FileTemplates\Client\Angular\ComponentTemplate\MainTemplate.txt (Create a MainTemplate.custom.txt file)

Replace this: import { NotifyService } from '@abp/notify/notify.service';

With this: import { NotifyService } from 'abp-ng2-module';

And this: {{DataTable_Import_Here}}{{TurboTable_Import_Here}}; import { Paginator } from 'primeng/components/paginator/paginator'; import { LazyLoadEvent } from 'primeng/components/common/lazyloadevent';

with this: import { LazyLoadEvent } from 'primeng/public_api'; import { Paginator } from 'primeng/paginator'; import { Table } from 'primeng/table';
0
AuroraBMS created 4 years ago
Also, how do we add styling for the NPOI excel exporting since the generation is still based on old method?

//var docDateColumn = sheet.Column(2); //docDateColumn.Style.Numberformat.Format = "yyyy-mm-dd"; //docDateColumn.AutoFit();
0

ismcagdas created 4 years ago
Support Team

Hi @AuroraBMS,

All those problems must be fixed now. Could oyu try with the latest version of AspNet Zero Power Tools ?

Thanks,
0

AuroraBMS created 4 years ago

Hi Ismcagdas,

The problem still persists.

I also especially downloaded the altest template and we still get this issue:

ERROR in ./src/app/main/systemSetup/queryManagers/queryManagers.component.ts Module not found: Error: Can't resolve '@abp/notify/notify.service' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\systemSetup\queryManagers' ERROR in ./src/app/main/systemSetup/queryManagers/queryManagers.component.ts Module not found: Error: Can't resolve 'primeng/components/paginator/paginator' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\systemSetup\queryManagers' ERROR in ./src/app/main/systemSetup/queryManagers/queryManagers.component.ts Module not found: Error: Can't resolve 'primeng/components/table/table' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\systemSetup\queryManagers'

This issue effects both normal components and also lookup tables.

Another thing that seems to either be changed or left out I am not sure which one is Tenant database migrations.

Our organization runs on multiple tenates which share some functions the same. in 8.2.1 we were able to during a table regeneration/creation in the generation console say "Y" update tenant databases as well. This feature doe not occure anoymore.
0

jaencalo created 4 years ago

Hi @ismcagdas,

So, currently, I can got the client side project running without errors, editing this lines on *.ts files in src/app/main/namespace/entityname directory:

//import { NotifyService } from '@abp/notify/notify.service'; import { NotifyService } from 'abp-ng2-module';

//import { Table } from 'primeng/components/table/table'; import { Table } from 'primeng/table';

//import { Paginator } from 'primeng/components/paginator/paginator'; import { Paginator } from 'primeng/paginator';

//import { LazyLoadEvent } from 'primeng/components/common/lazyloadevent'; import { LazyLoadEvent } from 'primeng/api/lazyloadevent';

I do not if it is the right solution, but works for me, awaiting for @ANZ Team RadTool new version...

Javier Carreño From Bogota, Colombia
0

ismcagdas created 4 years ago
Support Team

Hi,

Yes, those are correct usages. Could you share your AspNet Zero Power Tools version ? Version 2.2.1.1 should work fine.

Thanks,
0
AuroraBMS created 4 years ago
Hi @ismcagdas,

Version 2.2.1.1 worked fine for standard Compnent.ts files.

You will need to do the fix on the lookup tables as well.

ERROR in ./src/app/main/documentTracking/documentStatusTrackings/documentStatusTracking-user-lookup-table-modal.component.ts Module not found: Error: Can't resolve 'primeng/components/paginator/paginator' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\documentTracking\documentStatusTrackings' ERROR in ./src/app/main/documentTracking/documentStatusTrackings/documentStatusTracking-transactionDocument-lookup-table-modal.component.ts Module not found: Error: Can't resolve 'primeng/components/paginator/paginator' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\documentTracking\documentStatusTrackings' ERROR in ./src/app/main/documentTracking/documentStatusTrackings/documentStatusTracking-transactionStatus-lookup-table-modal.component.ts Module not found: Error: Can't resolve 'primeng/components/paginator/paginator' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\documentTracking\documentStatusTrackings' ERROR in ./src/app/main/documentTracking/documentStatusTrackings/documentStatusTracking-user-lookup-table-modal.component.ts Module not found: Error: Can't resolve 'primeng/components/table/table' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\documentTracking\documentStatusTrackings' ERROR in ./src/app/main/documentTracking/documentStatusTrackings/documentStatusTracking-transactionDocument-lookup-table-modal.component.ts Module not found: Error: Can't resolve 'primeng/components/table/table' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\documentTracking\documentStatusTrackings' ERROR in ./src/app/main/documentTracking/documentStatusTrackings/documentStatusTracking-transactionStatus-lookup-table-modal.component.ts Module not found: Error: Can't resolve 'primeng/components/table/table' in 'W:\BRM\BRM-8.5.0\angular\src\app\main\documentTracking\documentStatusTrackings'

ASLO, when generating a objects linked to each other with the Primary key as string and then having the lookup tables and so on generated i get the below issue:

ERROR in src/app/main/documentTracking/documentStatusTrackings/documentStatusTracking-transactionStatus-lookup-table-modal.component.ts:72:9 - error TS2322: Type 'string' is not assignable to type 'number'. 72 this.id = transactionStatus.id; I have no data set to int or number based instances and also no data is linked to numbers. everything is string based and the lookup tables generated this:

setAndSave(transactionStatus: DocumentStatusTrackingTransactionStatusLookupTableDto) { this.id = transactionStatus.id; this.displayName = transactionStatus.displayName; this.active = false; this.modal.hide(); this.modalSave.emit(null); }

** This.Id is read as an int/number transactionStatus.id is an string. This.id is also supposed to be a string.**

**##

Another thing that seems to either be changed or left out I am not sure which one is Tenant database migrations.

Our organization runs on multiple tenates which share some functions the same.

in 8.2.1 we were able to during a table regeneration/creation in the generation console say "Y" update tenant databases as well.

This feature doe not occure anoymore.**
0

ismcagdas created 4 years ago
Support Team

Hi @AuroraBMS,

We will fix those problems and release a new version as soon as possible.
0

musa.demir created 4 years ago

Hi AuroraBMS

First of all, sorry about the problems you came across. I created 3 issues about your problems. https://github.com/aspnetzero/aspnet-zero-core/issues/3157 https://github.com/aspnetzero/aspnet-zero-core/issues/3156 https://github.com/aspnetzero/aspnet-zero-core/issues/3155

We will fix them asap.
1

AuroraBMS created 4 years ago

Thanks for this one, guided me in the right directions: https://github.com/aspnetzero/aspnet-zero-core/issues/3157

Never knew about the actual tenant migration being triggered from the migrator.exe in the migration component.
0
AuroraBMS created 4 years ago
Just to add another bug to the power tools list:

When creating an entity follow the below steps to reproduce:

Start Creating Entity and add Navigation Property

After adding the navigation property edit and for instance change the name and click OK (This causes the entity data type to change which seems to break the application but is not the end yet)

After finishing the name change of the property, click delete.

This causes the application to freeze up and then restart visual studio automatically and in the end if you created a +-100 field entity with a bunch of navigation properties you have to start over again.

Maybe a feature suggestion for Power tools: Have an excel sheet import or something that is easily changeable or reimportable as navigation with large entities if you edit and save where it resets to the top of the list can be quite tough and time consuming. Just a thought though if it is relevant in any way.
0

ismcagdas created 4 years ago
Support Team

Hi @AuroraBMS

Could you create this bug report at https://github.com/aspnetzero/aspnet-zero-core/issues/new ? It will be better for us to track such bugs.

You can also create a separete feature request for us to evaluate.

Thanks a lot for your detailed tests.
0

AuroraBMS created 4 years ago

Hi @ismcagdas,

It has been logged. Thanks for the link, will log bugs/issues there going forward.
0

ismcagdas created 4 years ago
Support Team

Hi,

Really appriciate it.

Thanks :)

Have an answer to this question? Log in and write your answer.

# List of issues:

19 Answer(s)

I also especially downloaded the altest template and we still get this issue:

Another thing that seems to either be changed or left out I am not sure which one is Tenant database migrations.

Version 2.2.1.1 worked fine for standard Compnent.ts files.

You will need to do the fix on the lookup tables as well.

ASLO, when generating a objects linked to each other with the Primary key as string and then having the lookup tables and so on generated i get the below issue:

**##

Another thing that seems to either be changed or left out I am not sure which one is Tenant database migrations.

Our organization runs on multiple tenates which share some functions the same.

in 8.2.1 we were able to during a table regeneration/creation in the generation console say "Y" update tenant databases as well.

This feature doe not occure anoymore.**