Activities of "AuroraBMS"

Hi Guys,

If anyone can assist with the below it would be greatly appreciated.

I have currently activated all the hangfire functions and settings and struggling a bit with getting my head around the process of implementing recurring jobs etc.

The questions I basically have is:

Where should I create the Job execution component in the aspnetcore application side For example this: (The below code comes from the example provided by ANZ - I however dont quite understand how to implement it in the actual project) BackgroundJob.Schedule<GetServersJob>(x => x.ExecuteJob(null, new GetServersParamsInput()), TimeSpan.FromSeconds(10)) I want to check data continiously and update data during the day if something in another database has been updated.

I have the code for checking and also updating in the ANZ database ready but that is a minor to this whole scenario.

Does anyone have an example of a hangfire Job & Args implemented in aspnetzero angular/core? The part where the job gets setup with the say create customers if new data is available and that is check say every hour or so. For this I have looked through a lot of the questions here on the support portal as well as info on the aspboilerplate and various other points but I just can't figure out where and how to actually implement the functional side of hangfire jobs in this.

The data does not update frequently to place a burden on the system and I am trying to avoid creating an integration tool to write and update data externally.

any detailed guidence will be greatly appreciated as these kinds of implementations I am worried I will rather break the application then get it working.

Thanks in advance

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

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?