NorthScope 2019.04.12

Owned by Emma Greenwood
Last updated: Apr 16, 2019
5 min read

(Software Version: 2019.04.12 Database Version: 2019.04.12)

Release Date: April 12, 2019


New Features

(lightbulb) New Menu

Please see our FAQ article "NorthScope New Menu - Where did my page go?" for details on where pages have moved to within the system from the New Menu changes. 

System

NS-4043 The Manage Reports page was updated, and functionality was added to deploy and install reports more efficiently

The following buttons have been added to the toolbar:

  • Download – an icon that provides the following 3 options:
    • Download RDL – This allows users to download single or multiple .rdl files for specific reports that exist on the report server. This would be used if users wanted to edit a specific report.
    • Download Query – This allows users to download the .sql files for specific reports that exist on the report server. This is for quick reference on what SQL is used in the report.
    • Download Report Package – This allows users to download a file that contains all the report information required to backup your reports or migrate reports between systems. This is done as a special .nsrpt file. 
  • Import Report Package – This opens a page for users to import reports contained in a previously created “Report Package”.  When the page opens, users can click the “Browse” button and navigate to the folder that contains the report package (.nsrpt file) to import. Once a file is chosen, the contents of the report package are displayed in the grid including the Report Name and an indication of whether it already exists in NorthScope. For reports that already exist in the system “Overwrite Existing” will be displayed, otherwise “Add New” will be displayed. Users can select which reports to import by clicking the checkbox alongside the corresponding report then clicking the “Import Reports” button. Overwriting an existing report will not remove it from the report server but rather will move it to the Deleted folder on the report server. Deleted reports are not visible in the NorthScope UI but are preserved on the Report Server. Once the import is complete the Deploy Reports window opens for users to select the reports to be deployed to the report server.

The Deploy Reports button has been updated to provide a pop up window that shows the user a list of the reports that have been selected to be deployed, the Company or Companies in which the reports can be used, the status of the report (Deployed, Unknown, Not Deployed, Error), whether the report exists on the reports server (Yes/No), the Current Version, the Latest Version and any Error messages.  If a report is in the status of ‘Error’, a message will be displayed to explain why the report cannot be deployed and the ability to select that report will be disabled.  Once the user clicks Deploy Reports a message will pop up to confirm the deployment.  If a report exists on the report server and Deploy Reports is clicked the existing version of the report is moved to the Deleted folder on the report server.

The Manage Reports List View has been updated to include the following new columns and updates to existing columns:

  • Functional Area – previously called Module, displays the new Functional Area for the report.
  • Use in Company – previously called Companies, displays the name of the company or companies in which the report can be used.
  • Status – This column displays the status of the corresponding report (Deployed, Error, Unknown, Not Deployed). Previous reports will have the status of Unknown and will need the new Functional Area assigned to be re-deployed.  A report in the status of Error indicates that the report cannot be located on the report server.
    • Not Deployed - A report is shipped with NorthScope but has not been deployed to the report server.
    • Unknown - The report definition exists in NorthScope but is incomplete, please contact NLP Support if you see this status
    • Error - Either the report definition does not exist in NorthScope or something happened during the deployment of the report.  Please try to deploy the report again to see the Error.
    • Deployed - A report definition exists in NorthScope and the report exists on the report server.
  • System Version – This column displays "Yes" when reports are shipped with NorthScope and have not been customized, otherwise this value will be blank.


Improvements 

Fisherman Accounting

NS-4377 Added Delivery Number to the Fish Ticket Void/Correct Screen

To allow users to easily select a batch of tickets to Void or Correct, a new “Delivery #” field has been added to header of the Void/Correct page. If something is entered in this field, tickets where the Delivery Number contains the value entered will be selected. In addition, a new column for Delivery # has been added to the results grid. This column is not in the system view but can be added to a custom view.

NS-4379 Added the ability for users to specify an ‘End Date’ to Fish Ticket Taxes and Premiums

To allow users to manage Fish Ticket Taxes and Premiums that apply for a specific date range, a new property for ‘Landed Date End’ has been added to the Fish Ticket Taxes and Premiums. The existing property of ‘Start Date’ has also been renamed to ‘Landed Date Start’ to provide more clarity as to which ticket date is used. The List Views have been updated to include the new ‘Landed Date End’ property and the name change to ‘Landed Date Start’. The ‘Landed Date End’ column was not added to the System View but can be added to a custom view.

If a user needs to add a ‘Landed Date End’ value to a Fish Ticket Tax or Premium, the value must be >= to the ‘Landed Start Date’. Taxes or Premium without a ‘Landed Date End’ value never expire (unless set as Inactive).

New and corrected tickets will auto-apply all Active Taxes and Premiums using both ‘Landed Start Date’ and ‘Landed End Date’. The Manual Premiums drop-down on the Fish Ticket Record View will only display the list of manual premium programs where the landed date of the ticket falls between the start and end date of the premium.

Bug Fixes

Fisherman Accounting

NS-4352 Fixed a bug with editing posted Fish Tickets

If a user was editing one of the editable values on a posted ticket, and the ticket contained a GL Date in a closed Fiscal Period, they were receiving a message stating that the fiscal period was not open. This validation should not happen because none of the editable fields on a posted ticket have financial significance.


Technical Changes 

Schema Changes 

ALTER TABLE dbo.ERPx_RSReport DROP CONSTRAINT FK_ERPx_RSReport_ERPx_MFModule

ALTER TABLE dbo.ERPx_RSReport DROP COLUMN ModuleSK

ALTER TABLE [dbo].[ERPx_MFSysPreferences] ALTER COLUMN [FunctionalAreaSK] [bigint] NOT NULL

ALTER TABLE [dbo].[ERPx_APProgram] ALTER COLUMN [APProgramID] [varchar] (50) NOT NULL

ALTER TABLE [dbo].[ERPx_APProgram] ALTER COLUMN [APProgramName] [varchar] (100) NOT NULL

ALTER TABLE [dbo].[ERPx_APProgram] ALTER COLUMN [PaymentFrequency] [varchar] (100) NULL

ALTER TABLE [dbo].[ERPx_APProgram] ALTER COLUMN [LastUser] [varchar] (100) NOT NULL

ALTER TABLE [dbo].[ERPx_APProgram] ADD [APProgramEnd] [datetime] NULL

ALTER TABLE [dbo].[ERPx_APTransactionMoreActionsCriteria] ADD [DeliveryNumber] [varchar] (50) NULL

ALTER TABLE [dbo].[ERPx_APTransactionMoreActionsCriteria] ALTER COLUMN [TransactionID] [varchar] (250) NULL

ALTER TABLE [dbo].[ERPx_MFModuleForm] ADD [FunctionalAreaSK] [bigint] NULL

ALTER TABLE [dbo].[ERPx_MFModuleForm] ADD CONSTRAINT [FK_ERPx_MFModuleForm_ERPx_MFFunctionalArea] FOREIGN KEY ([FunctionalAreaSK]) REFERENCES [dbo].[ERPx_MFFunctionalArea] ([FunctionalAreaSK])

ALTER TABLE [dbo].[ERPx_MFModuleForm] DROP CONSTRAINT [DF_ERPx_MFModuleForm_SecuritygroupCategoryEN]

EXEC sp_RENAME 'ERPx_MFModuleForm.SecurityGroupCategoryEN' , 'FormCategoryEN', 'COLUMN'

ALTER TABLE [dbo].[ERPx_MFModuleForm] ADD CONSTRAINT [DF_ERPx_MFModuleForm_FormCategoryEN] DEFAULT ((6)) FOR [FormCategoryEN]

ALTER TABLE [dbo].[ERPx_MFSysPreferences] ADD [FunctionalAreaSK] [bigint] NULL

ALTER TABLE [dbo].[ERPx_MFSysPreferences] ADD CONSTRAINT [FK_ERPx_MFSysPreferences_ERPx_MFFunctionalArea] FOREIGN KEY ([FunctionalAreaSK]) REFERENCES [dbo].[ERPx_MFFunctionalArea] ([FunctionalAreaSK])

ALTER TABLE [dbo].[ERPx_RSReport] ADD [FunctionalAreaSK] [bigint] NULL

EXEC sp_rename 'dbo.ERPx_RSReport.FileLocation', 'ReportPathOverride', 'COLUMN'

ALTER TABLE dbo.ERPx_RSReport ADD CONSTRAINT FK_ERPx_RSReport_ERPx_MFFunctionalArea_FunctionalAreaSK FOREIGN KEY (FunctionalAreaSK) REFERENCES dbo.ERPx_MFFunctionalArea (FunctionalAreaSK)