Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "AuroraBMS"

Thanks Ismcagdas,

After going through the support forum, this is literally 100 times easier than what some people went through to implement hangfire for tenants usage.

Works great!

Thanks again!

Hi Ismcagdas & Bobingham,

Thank you for the assistance.

If I can make a suggestion regarding the documentation segment. Please add the hangfire links "guide" that Bobingham shared to the Aspnetzero documentation.

It is the most detailed bit regarding hangfire and since the placement of the files was one of the most confusing components, this one shows in details how to handle hangfire.

Thanks again!

Hi @ismcagdas,

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

Just to add another bug to the power tools list:

When creating an entity follow the below steps to reproduce:

  1. Start Creating Entity and add Navigation Property
  2. 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)
  3. 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.

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.

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.**

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.

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();
				

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';

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';
Showing 31 to 40 of 54 entries