This help page does not exist for the integration
We have released new functionality for graphs in reports published for all our customers October 2nd, 2023.
The functionality includes
See the course “Graphs in OneStop Reporting” on Visma Learning Universe for more information:
Data access will no longer be available on Role level, but is moved to User in the New Administration. It is the same procedure on Company level as Client.
NOTE: Limited access to companies must be given on the User level in the Old administration.
We have upgraded the Date Picker with a new design.
Select a single date, a period, or a date range. Click on the arrows, the month, or the year to get a wider range.
Places where you can find the Date Picker
Choose a single date, a period or a date range. Click on the arrows, the month, or the year to get a wider range.
We have added a report label for “Inspirational templates” under Report type. Inspirational templates are report templates that are meant to be used as inspiration for report creators when they are creating their own templates. With the added label for such reports, you can decide on who gets to see these report templates.
We have disabled the Save button in Data Manager after users have clicked Save. In this way, there is no confusion if changes have been saved.
Fixed a typo in the Norwegian text for the status of data in reports. Text is now “Data ble oppdatert for X tid siden”.
We have fixed an issue when users are storing budget values if sheet per value name is larger than 50 characters.
We have fixed an issue where Line Item Details would not always be activated when description/name were used for sheet per value.
Bugs & Feature Req. | Integration | Module | Factset/Dimension | Attribute/Measures | Comment |
Bug | Business NXT | Multiple | General Ledger/ Companies for group Reporting | Multiple | Enhanced performance of group reporting based on General Ledger Transactions by adding indexes to database. |
Bug | Business NXT Live | General Ledger | Budget Lines | N/A | Fixed an issue where saving budget data would, in some instances, change budget data in other scenarios where transactions had equal line numbers. |
Bug | Business NXT | Budgeting | Fixed Line Item Details not always activated when description/name is used for sheet per value | ||
Feature | Visma Business
Business NXT Business NXT Live |
Multiple | R-dimensions | GR X Description | Added an attribute for the description of GR (Group) fields. |
Feature | Visma.net | Sales | Sales Order | Added “Unit of Measure” in Salesorder |
We have made the following fixes for Budgeting:
We have added endpoint-to-model mapping for all integrations. Reports should now correctly display when data was last updated.
We have fixed a typo where an English word appeared in the Norwegian translation (Roles-Roller).
We have fixed an issue where parameter chaining didn’t work when an assignment had the Let user decide option.
In Data Manager, we have removed rows from ExtDimProject, that are not linked to existing project.
In Get Data, we have added Modify datetime filter to the Project endpoint to improve data imports.
We have fixed an issue where fields in Data Manager were left empty after saving data (EntityKey did not update correctly for extension tables when the ODP company Id changes).
Bugs & Feature Req. | Integration | Module | FactSet/Dimension | Attribute/Measures | Comment |
Feature Request | Visma Business / Business NXT / Business NXT Live | Sales Orders | Document Order Lines | Period & Product | Added a link to Period and Product in Document Order |
Feature Request | Multiple | Period Functions | Added period function “This Quarter Last Year” to Report Designer | ||
Bug | Visma Business / Business NXT / Business NXT Live | System | This Company | Added missing Finnish translations | |
Feature Request | Visma Business | Document | Added DocumentId to FactSet Document | ||
Feature Request | Visma Business / Business NXT / Business NXT Live | Product | Product | Added a link to Source Country in the Product dimension | |
Feature Request | Visma Business / Business NXT / Business NXT Live | Multiple | Multiple | GR-fields | Added a group description with translation depending on user settings |
We are pleased to announce that the Duett integration is now available for all customers.
We have added the possibility for customer administrators to label reports distributed from OneStop Reporting as “internal” or “external”.
Users can now use labels to filter reports.
To filter on labels;
We have added statuses for data imports to the Reporting window. The displayed text differs from Cloud and On-Premise integrations
We have fixed the following issues:
We have fixed an issue where some account groups were not available for customers with a customized chart of accounts if the chart of accounts were edited before the release of new account groups.
We have decreased the maximum number of days for scheduled imports to 5 days. This enforces fetching data based on last changes for scheduled imports, instead of transaction date. Existing scheduled import jobs are automatically updated. No change to manual import jobs. This will result in better data reliability and faster imports.
Bugs & Feature Req. | Integration | Module | Factset/Dimension | Attribute/Measures | Comment |
Feature Request | Visma Business / Business NXT / Business NXT Live | Finance | Update Voucher | Multiple | Added new FactSet for Updated Voucher |
Bug | UniEconomy | Group Reporting | Multiple | Fixed an issue with fkEntityKey to improve the performance and execution time of many group reports | |
Bug | 24 SevenOffice | System | This user | Changed the display name of the module system and the FactSet This user. Previously the display name was “0” | |
Feature Request | Visma.net | General Ledger | Added Filter to Financial Period. Now the imports for Custom Date work without errors | ||
Bug | Visma Business / Business NXT / Business NXT Live | Capital Asset | Capital Asset Balance | Multiple | Added new FactSet for Capital Asset Balance |
Feature Request | Softrig, UniEconomy | Group Reporting | Fixed an issue where the companies for Companies For Group Reporting would not be fetched correctly | ||
Bug | Visma Business / Business NXT / Business NXT Live | Sales Orders | Multiple | Multiple | Added Finnish translations for Order Type and Trans Type |
Feature Request | Visma.net | Accounts Payable | Supplier Invoice Lines | Multiple | Added discounted prices to Supplier Invoice Lines |
Feature Request | Visma.net | Multiple | Multiple | Updated API for Earning Type Dimension to fix the link in Project Transactions Factset, added a link to Time Card Summary Factset | |
Feature Request | Visma.net, Tripletex, Visma Business, Business NXT, Business NXT Live | Period functions | Added 24 months rolling period function |
We have changed the name of tenants to clients in English, and “klienter” in Norwegian, Swedish, and Danish.
We have moved Add/Remove extensions to New Administration > client > Client settings.
We have changed the term “Members” to “Users” in Roles.
We have removed Main line as an alternative when making adjustments in Spreading and Line Item Details and replaced it with Current line.
We have added some missing translations to Danish and Finnish.
We have fixed an issue where =WEEKNUM(XXX;21) would not return the correct number of the week.
We have fixed an issue where it was not possible to view all details on budget templates.
We have fixed an issue where parameters would not update correctly when removing/adding templates to a workflow.
Bugs & Feature Req. | Integration | Module | Factset/Dimension | Attribute/Measures | Comment |
Feature Request | Visma Business / Business NXT / Business NXT Live | Customer, Supplier | Customer Balance, Supplier Balance | Added new calculated fields to Customer and Supplier Balance | |
Feature Request | Visma.net | Sales | Shipments | Invoice Number | Added new field: Invoice number to Shipments. The user should now be able to much easier create reports that contain data about orders, shipments and invoices. |
Feature Request | Business NXT API | Multiple | Scenario | Removed possibility to store data to dimension OSR Scenario. OSR Scenario will no longer show up as a dimension in Data Manager | |
Feature Request | 24SevenOffice | GL | GL Transactions | Added support for up to 20 user defined dimensions in the General Ledger factset (up from 5) | |
Feature Request | Visma Business / Business NXT Live | Finance | Budget Transactions | Added storage to field: budgetlinetype in the Budget transactions factset (BgtLn). Users will now be able to save data to this field | |
Feature Request | Multiple | Multiple | Multiple | Added support for Excel formula WEEKNUM (return value gives the day the week begins, helpful for reporting) | |
Bug | Visma Project Management | Project Management | Project Fee/ Period | Added link between product cost and period based on eventDate | |
Bug | Visma.net | Time Card | Time Card Summary/Projct fixed | Fixed the link to the Project fixed dimension in Time Card Summary | |
Feature Request | Visma.net | Multiple | Inventory | Multiple | Added fields from packaging (Weight, WeightUoM, Volume, VolumeUoM) to the inventory dimension |
Feature Request | Visma.net | Timecard | Multiple | Added English translation for Time Card and Time Card Summary | |
Feature Request | PowerOfiice GO | General Ledger | General Ledger Transactions | IsReversed | Added attribute IsReversed to General Ledger Transactions |
Feature Request | Visma Project Management | Project Management | Project Travel Expenses | Multiple | Added new factset: Project Travel Expenses |
We now support the Excel-function Merge & Center in expanded rows and columns in the portal.
Previously, this function was only supported in Report Designer, and in the portal in instances where groups did not expand.
This change will affect existing reports (if Merge & Center is in use) as well as all new reports.
NOTE: There might be instances in certain report designs where Merge & Center is still not supported. Create a support-ticket through the partner portal or Support.osr@visma.com if you experience this issue.
We have added new columns to the User tab in the new Administration:
We have added the possibility to assign or unassign roles for a user from the settings for a user on the Users tab.
We have added the possibility to distribute a report with the same tenant as source and destination.
We have fixed an issue where information fields for budgeting template details were missing.
We have fixed an issue where very large user reports timed out.
We have fixed an issue where users who had both Business NXT integrations would only display Dashboard data from the Live integration.
Bugs & Feature Req. | Integration | Module | Factset/Dimension | Attribute/Measures | Comment |
Feature Request | Business NXT API, Business NXT Live | Multiple | Multiple | Week | Added new fields for TransactionWeek based on the voucher, value -and due date. |
Feature Request | Visma Global | Multi Company Reporting | Global Company Budget Foundation | FreeDimension | Added FreeDimension (OSR specific dimension in Data Manager) to Multi Company Reporting. NOTE! MCL Setup has to be run before this change will take effect. |
Feature Request | Tripletex | Accounting | Budget Transaction | Implemented a new endpoint for budgets. OSR now fetches all budgets (Company, department, project, product, and employee). | |
Bug | Tripletex | Fixed an issue where budget data was missing | |||
Feature Request | Visma Business, Business NXT API, Business NXT Live | Multiple | Multiple | Added R-fields as normal attributes to Customer and Supplier. Also added these to the Multi-Company solution | |
Feature Request | POGO | Time Tracking | Time Tracking Entry | Added a new solution for time-transactions for POGO. The Time Tracking factset has been updated with a lot of new fields. | |
Bug | Visma Business, Business NXT API, Business NXT Live | Finance | Budget Transactions | Changed the link type for Account in the Budget transactions Factset. Transactions without an account should now appear in Data Manager | |
Bug | Visma.net | Multiple | Fixed a data-import error for WareHouseLocations. | ||
Bug | Visma.net | Project Management | Customer | Fixed an error that caused storing for ext. fields to fail | |
Bug | Visma Business | General Ledger | Voucher | Fixed an issue where values from December differed when running a report for the whole year compared to running it exclusively for December | |
Feature Request | Visma Business, Business NXT API, Business NXT Live | Finance | Account | Added new endpoint: Account Type | |
Feature Request | Visma Business, Business NXT API, Business NXT Live | Finance | Batch | Added new endpoint: Batch | |
Feature Request | Business NXT API, Business NXT Live | Multiple | Multiple | Added new endpoints: Accounting Documents, Approval Tasks, and Approval Task Log Change |
With Roles and Labels it is possible to distribute specific reports to specific users.
Report labels are selected for each report and role, then users are added to roles.
Which reports the user will have access to depends on the user’s role.
NOTE: Only administrators at the top (customer) level are able to edit this setting.
To turn on the functionality for Roles and Labels, the setting must be selected at the customer level. Before the setting is selected, Roles and Labels will have no effect.
In this way, you can create roles, add users to roles and add labels to reports without it affecting your OneStop Reporting environment before you are ready.
NOTE: If labels are not added to reports and users are not given roles, reports will not be available for users if the setting is selected.
All reports distributed from OneStop Reporting have predefined labels which cannot be changed. These labels are determined by Visma Software in the country where you purchased OneStop Reporting.
NOTE: Only administrators can add labels to reports. The Administrator must be an administrator at the same level or a higher level than the report is distributed.
Consequently, if a report is only distributed to one tenant, a tenant administrator can add labels to the report, if a report is distributed to a group, a group administrator can add labels, and if a report is distributed at top level only a top level administrator has access to add labels.
To add labels to reports;
NOTE: Only top-level administrators can create roles for distribution.
NOTE: Administrators at all levels (top, group, or tenant) can add users to roles.
For a report to be visible to a user, the labels of the user’s role must at least have one matching label in all of the four types. The different types are: Budget type, Internal/external, Period type, and Report type.
An example is shown in the picture below.
In this example, the user will not have access to the report as none of the labels match the report type. If one of the labels Budsjett, Hovedbok, or Kunde is added to the role, this report would be visible to the user.
In the picture below, a role for all sales employees in a company is created.
The reason why the particular labels and label settings are selected is explained below.
The setting Include all labels in group is selected on Budget Type and Period Type.
This is because all sales employees should have access to all reports regardless of the type of budget and periods being used. If more budget or period types are added to reports in the future, the sales employees will also have access to these as long as the reports fit the other criteria.
It is further chosen that the sales employees should only have access to reports with the labels: Internal, Project, Sales, and Hour. If more labels are added to these groups in the future, the sales employees will not automatically gain access.
We have released a new version of Report Designer. The new version contains:
NOTE: Remember to download the latest version of Report Designer to take advantage of new functionality.
You can always find the latest version of Report Designer here. Alternatively, you can open Report Designer and click Yes on the popup message that opens.
The reports with enhanced performance are built on new factsets for historical customer- and supplier transactions.
We have added a new type of parameters called Initial parameters. Using Initial parameters makes Report Designer able to only request data that is relevant for the specifics of the report the user is making. In the case of the historical customer- and supplier transactions, this is based on the historical date. Previously, Report Designer retrieved larger amounts of data, then cleaned it to only include the necessary data.
The functionality for Initial Parameters is supported in the following factsets:
These factsets are duplicates of the old factsets and these are now named Historic Supplier Transactions DEPRECATED and Historic Customer Transactions DEPRECATED.
In this way, this release will not affect any customized reports.
Reports distributed from OneStop Reporting NO will be converted on an ongoing basis.
When you drop the attribute in the sheet, you will get the following options:
NOTE: This dialog will only appear the first time an attribute is used from a factset supporting Initial parameters in a report.
The Initial parameter filter will be created based on the attribute Historic Date (the date you want to see the status of the historic transaction for).
4. .Click Create the filter and add a report parameter.
5. Create a group based on the selected attribute in the normal manner.
NOTE: From this point, you can continue building the report as normal.
6. Go to the Sheet filters in the Layout Editor.
7. Click Initial Filter.
The Initial Filter tab is new. On this tab, the initial parameters enhancing the performance will appear.
Initial parameters will always appear on the sheet level and cannot be added to groups on columns, rows, or cells.
It is not possible to delete these filters from the Layout Editor manually.
The filters will automatically disappear if the report no longer contains any attributes from the factsets supporting Initial parameters.
To edit the parameter of the initial filter, continue with the following steps:
8. Click OneStop Reporting on the ribbon.
9. Click Report Parameters.
10. Click to ? Edit the Initial Parameter.
11. Write a suitable Prompt text and continue editing the filter as normal.
12. Finish your report and enjoy the enhanced performance!
Users with an older version of Report Designer will not be able to save reports that have previously been edited and saved in the latest version of Report Designer.
It is therefore recommended that all users in the same OneStop Reporting environment update to the latest version so all users will be able to edit and save reports as normally.
NOTE: Users with an older version will be able to open and edit reports in Report Designer, but will not be able to save the changes (As long as the report in question has been opened and saved by a user with the latest version).
To convert reports to run on the new factsets with enhanced performance, all data based on attributes from the old factset must be replaced with the same attributes from the new factsets. Among others, this includes fields used as filters, Grouping/ Sorting, parameters, and directly in the Excel sheet.
NOTE: Best practice is to duplicate the original report before you make any changes. By making a duplicate, you will always have a copy of the original.
If elements from the old factsets are used in the report, it will not be possible to save the changes. It might be useful to build the report from scratch using the new facets to avoid saving issues if not all old elements are replaced.
NOTE: Because it is not possible to save changes in reports including elements from the old factsets, the report must be converted before you make any changes. The naming of the old factsets is shown in the picture below.
We have added new functionality to better manage deleted expressions in Report Designer.
Previously, reports containing deleted expressions would fail when clicking Run without much information on how to solve the problem.
How does it work now?
When deleting an expression in use, the user will get the following warning message.
If the Expression is deleted anyways and the user saves the report, a warning will occur informing the user of what expression should be removed from the report definition.
This warning message will also be presented whenever opening a report in Report Designer which includes a deleted expression.
When looking at filters in the report, the filter of a deleted expression will be presented as shown in the picture below:
The user has two options to fix the issue:
When using this solution, the deleted expression will return in every invalid expression filter of the expression in question.
When running reports that include deleted expressions in the portal, the following message of error will be displayed.
We have updated the OneStop Reporting logo in Report Designer.
We have added the following edit options to Tenant settings in the New Administration:
Data Manager: We have fixed an issue where, for some users, the extension fields would show in the Lookup for multiple companies.
Data Import: We have increased the maximum number of days the user is allowed to use in scheduled data-import jobs from 100 to 200. The user will have to update their import jobs for this change to take effect. This should help companies that are struggling with fetching older data being changed.
Bugs & Feature Req. | Integration | Module | Factset/Dimension | Attribute/Measures | Comment |
Bug | Tripletex | DimProject | Fixed an issue where projects older than 30 days were not updated properly (e g name, project customer, project category et c) | ||
Feature Request | Business NXT API | General Ledger | Voucher | Added Voucher (WaVo). New factset in General Ledger. | |
Feature Request | Visma Business | Group Reporting | Global Orders | Added Orders to MCL. New Factset in Group Reporting. | |
Bug | Visma Business, Business NXT API, Business NXT Live | Multiple | Fixed an issue where the drilldown would be duplicated due to Voucher Series | ||
Bug | Visma.net | Project Management | Improved Workhours endpoint by adding the LastChange and FromTime filter. Added deletion workhours endpoint to include deleted entries. | ||
Bug | Visma Business | Group Reporting | Fixed an issue where the MCL setup would fail on OSRTransactionTypeMCL. | ||
Bug | Visma Business, Business NXT API, Business NXT Live | Multi-Company Reporting | Global Products | Fixed the link between Global Product and Product Transaction | |
Feature Request | Visma.net | PM | Project | Added new endpoint Project Keywords linked to Project Dimension | |
Feature Request | Visma.net | Inventory | Added Intrastat details to Inventory Dimension |
We are proud to present our new logo for OneStop Reporting! The new logo is designed to fit in with Visma Software’s family of cloud products. The new logo has a simple and elegant design that signals our affiliation with Visma and our ambition to deliver the best solutions for reporting and budgeting in the cloud.
The new logo will be visible on all our products and services, including our website, our apps, and our reports. We hope you like the new logo as much as we do!
It is now possible for customers to decide which of OneStop Reporting reports to distribute.
Previously, distribution was an all-or-nothing solution, where all OneStop Reporting reports would be distributed or none of the reports would be distributed.
The new settings can be found in New Administration on two different levels; top level (Customer settings) and tenant level (Tenant settings).
The distribution settings affect how actions made in the distribution module will behave.
If the setting Allow receiving reports from OneStop Reporting is switched ON at the customer level, it will override the setting for all tenants.
If it is turned OFF at customer level, it is still possible to turn it ON for specific tenants.
If the setting has been set ON at tenant level, and the customer setting is later turned OFF, the setting of the tenant will not be affected. Meaning that Allow receiving reports from OneStop Reporting will still be ON for the tenant.
In other words:
If the setting at the tenant level has never been edited, it will always follow the setting on the customer level.
NOTE: To edit the settings for the top level, you must be a top level (customer) administrator.
Click the pencil to edit the settings:
The setting Allow receiving reports from OneStop Reporting is by default turned on for all new customers since the setting was created. The setting provides access to reports distributed from OneStop Reporting.
NOTE: Top level, group level, and tenant administrators are able to edit this setting.
Click the pencil to edit the settings.
Only selected reports will be available if the mode Only distribute selected reports is set by a top level administrator.
NOTE: You need to be a top level administrator to determine which OneStop Reporting standard reports should be distributed in your OneStop Reporting environment..
To determine which OneStop Reporting reports should be available in your OneStop Reporting environment do the following steps:
You can easily get an overview of which reports are included and excluded based on the appearance of the report; included reports appear as normal while the excluded reports are grayed out.
Important: If the Distribution mode Distribute all reports is active, it will have no effect if reports are included or excluded in the Distribution module. All reports will be visible for users accessing the Reporting module either way.
In the picture above, the reports “0.1 Månedlig rapportpakke” and “1.0.1 Full oversikt – Denne perioden” are included and therefore visible for users with access to the Reporting module.
The reports “0.1 Månedlig rapportpakke med OSR budsjett” and “1.0 Nøkkeltallsanalyse” are not included in the distribution and are not visible to any users in the Reporting module.
As you may have noticed, we are currently working on a completely new administration page that caters to easier management of users, tenants, groups, and customers in OneStop Reporting. While we are working on the new features, we have released a preview of the new administration page.
In this release we have moved the following functionality to the New Administration page:
In the past, only the owner of a workflow could edit or delete that workflow. We have now made it possible for administrators to edit and delete workflows created by other users.
It is now possible to budget with the Visma Business NXT Live integration. Previously, it was only possible to budget with the Visma Business NXT integration.
With Visma Business NXT Live you can run reports for individual companies on live data as well as do budgeting. If you have no need for group reporting, we recommend that you only use this integration.
You should use the Visma Business NXT integration if you need to do group reporting. The integration is connected to the API of Visma Business NXT and data is retrieved every night, provided that nightly import jobs have been set up. Note that it is possible to set up the data sync manually at other times. Budgeting is now also available with this integration. Nevertheless, it is recommended to use the Visma Business NXT Live integration for budgeting, so that actual figures are displayed in real-time. The possibility to budget with the Visma Business NXT integration will be removed in the future.
In Business NXT, budget data is stored in OSR Budget Foundation, not in Budget lines. OSR Budget Foundation is OneStop Reporting’s own budget tables and contains extended functionality.
Budget lines is the budget table from Visma Business and Business NXT.
If you have saved your budget with the Visma Business NXT integration to OSR Budget Foundation, you will need to move the budget data before continuing the budgeting process. OSR Budget Foundation is available from the Live integration as well, but data is stored in two different locations. With the Visma Business NXT integration, data stored in OSR Budget Foundation is saved in OneStop Reporting and with the Live integration, data is stored in OSR Budget Foundation in Business NXT.
If you need assistance, please contact konsulent.konsulent.osr@visma.com.
If you have customized budgeting templates, contact konsulent.osr@visma.com for assistance with converting the templates to the Business NXT Live integration.
If you are doing your budget at group level, budget data should be stored in Budget Lines with the Visma Business NXT Live integration. Then data can be fetched and shown at group level with the Visma Business NXT integration.
The dimensions available in the Data Manager module contain OneStop Reporting extension fields. These fields can be used to add additional information to existing dimensions such as Account, or to create new tables, for example, for handling currencies.
If you don’t need group reporting, you can use dimensions from Data Manager with the Live integration for budgeting and reporting.
If you are going to use dimensions from Data Manager for group reporting as well as reporting on individual companies with the Live integration, input in the dimensions must be maintained in both integrations. This is because data stored with the Business NXT integration is stored in OneStop Reporting, while data stored with the Business NXT Live integration is stored in Business NXT.
If you are only using the dimensions for group reporting, you currently only need to maintain the dimensions in the Business NXT integration. It is still recommended to maintain the same input in the Visma Business NXT Live integration, as storage through the Visma Business NXT integration will be removed in the future.
Publisher: We have fixed an issue where summer/winter time could disrupt the publishing time of reports.
Reporting: We have fixed an issue where options and report information didn’t show in Listview and in Favorites under the Reporting module.
Bugs & Feature Req. | Integration | Module | Factset/Dimension | Attribute/Measures | Comment |
Bug | Visma.net | PM | FactInvoiceRows / Workhours | Quantity | Fixed link connection between Invoice, Invoice Row and Workhours and Project Fees. Now user can display quantity from Workhours and Project Fees and group it by Invoice Row Description and Invoice Number, |
Bug | Visma.net | Inventory | Inventory Units | Fixed problem with Inventory Units, now all units sets (from, to) are displayed for each inventory. Please note that full import is needed for Inventory Unit job | |
Bug | Visma.net | PM | Project | Fixed issue with Invoice Total attribute in Project Dimension | |
Bug | Visma.net | PM | Project Forecast | Fixed problem with Project Forecast, now the forecast amounts display correctly for each project | |
Bug | Visma.net | Project Budget | Project Accounting | Fixed an issue where Project Tasks would be linked to wrong projects. | |
Bug | Visma Business | Multiple | Multiple | Removed duplicated Finish Date attribute | |
Feature Request | Power Office GO | Multiple | Project | Added FixedPrice (Fastpris) and Billable Rate (Timepris) to the Project dimension | |
Feature Request | Visma Business, Business NXT | System | Added link to OSRCompany for Global LockedDate | ||
Feature Request | Power Office GO | GL Transactions | Outgoing Invoice Lines | Added new fields to Outgoing Invoice Lines | |
Feature Request | Visma Business | Finance | General Ledger | Added Voucher Series table and linked to the voucher number | |
Feature Request | Visma Business, Business NXT Live | Multiple | Multiple | Added new fields (GenAcNo, VoNo. JNo and EntNo) to Historical Supplier and Customer Transactions |
All GL fields are now created as dimensions in Report Designer and can be used to edit and build templates. NOTE: This change will not affect any existing reports.
Previously, only GL1 and GL2 were available in OneStop Reporting as dimensions, while GL3–GL5 were only available as attributes.
By using dimensions as parameters in templates, users will be able to view additional information about the particular GL field.
The GL fields that are in use by the company will show up as dimensions in Report Designer.
The naming of the fields is dependent upon how the customer has named the fields in Xledger. If GL3 is named Cost Center in Xledger, the name of the dimension will be GL 3 Cost Center in OneStop Reporting.
NOTE: The old GL attributes used in existing templates can now be found under More Fields.
It is possible to add information to the GL dimensions beyond what’s available from Xledger.
To do so;
NOTE: If OneStop Reporting Extension fields are in use in the old dimensions and you want to switch, the information added in the old extension fields must be added to the new dimension manually.
We are pleased to announce that budgeting is now available in the Business NXT Live integration. This update also includes storage of budget data directly to Business NXT.
We have added a warning message to all users when there is an end date for their subscription. This is an important message because after the subscription has ended, the customer will no longer have access to OneStop Reporting. If you get this message and suspect that this is an error, please contact your OneStop Reporting administrator.
We have also updated the warning message users get when they are deleting a tenant. The new message includes more information about the consequences of deleting the tenant.
After last month’s update of SpreadJS, some users experienced that the Drill-down tool to see underlying transactions was not working. We have fixed the issues and drill-down is now working properly.
We have fixed an issue where Visma Business users have experienced that after duplicating a report in Reporting, the duplicated report would run slowly.
Dimensions names for Department (Avdeling R1) and Projects (Prosjekt R2) have had the same name appear when selecting a dimension in Data Access filter (in Administration) or Data Manager. This issue has now been fixed and the dimensions have new distinct names.
Bugs & Feature Req. | Integration | Module | Factset/Dimension | Attribute/Measures | Comment |
Feature Request | Tripletex | Invoice | SupplierInvoice | Multiple | Added Supplier Invoice Order Lines Factset linked to Supplier Invoice, to get more details about e.g. count (Antall) Dimension: Supplier Invoice (Leverandør faktura) Module: Invoice (Faktura) |
Bug | Visma.net | PM | Fixed an issue where hours in PM did not update correctly for some customers. | ||
Bug | Visma.net | PM | Fix to incorrect project cost (fields total Product Cost -> Factset: Project Fees and total Personal Cost -> Factset: Workhours have been added to get the correct sum of Project Cost) Module: Project Management | ||
Bug | Tripletex | Logistics/Warehouse | Product | Fix where Warehouse/Logistics module didn’t show product information | |
Feature Request | Visma.net | Financials | FactSupplierDocument | Multiple | Voucher Link added to FactSupplierDocument |
Bug | 24SO | Multiple | Transaction Type | Description | Fixed an issue where Description of Transaction Type did not match data from 24SO |
Bug | PowerOffice Go | GL | Account | Fixed issue where Account Number didn’t show up in drilldown | |
Feature Request | Visma Business | Group Reporting | Fixed a translation error with Lock Date in group reporting | ||
Bug | Xledger | Data Manager | Renamed GL dimension(s) in Data Manager | ||
Bug | Tripletex | Customers / Suppliers | Fix where some payment information for Customers and Suppliers was missing | ||
Feature Request | Visma Business,, Business NXT Live | Multiple | Voucher | Added voucher table (WaVo) for not updated vouchers |
We have fixed an issue where duplicated templates would get incorrect names in List view. NOTE: This did not happen to users who were using the default Card view.
We have upgraded our report viewing tool to SpreadJS version 16.
We have fixed an issue where the error message for saving did not appear.
We have updated the warning message users receive when deleting tenants. The new message has more information about the consequences of deleting tenants.
Bugs or feature | Integration | Module | Factset/Dimension | Attribute/Measures | Comment |
Feature | Business NXT Live, Visma Business, Business NXT | General Ledger | Period | Multiple | Created calculation for periodID in cases where the value of period was 0. |
Feature | Tripletex | Invoice | SupplierInvoice | Outstanding Amount | Added Outstanding amount for supplier invoices. |
Feature | Tripletex | General Ledger | Parent Project -> MainProjectNumber-Name | N/A | Fixed an issue where dimensions would have equal names in some instances. This was related to language issues. |
Feature | PowerOffice Go | Multiple | Project | Multiple | Improved performances of some reports that timed out related to the Project dimension. |
Feature | PowerOffice Go | Multiple | Department ->Project Department (Prosjektavdeling) Employee ->Project Manager (Prosjektleder) Employee ->Budget Manager (Budsjettansvarlig) | N/A | Changes names of dimensions with equal names to make it easier to distinguish dimensions in Data access filters. |
Version: v5.2.30709.0843
You can now customize the default drilldown view to display fields of your choice and in the order of your preference.
NOTE: You need the Can customize drilldown layout permission to customize the drilldown view.
NOTE: The drilldown view you specify is global (within a company). If you, for example, drill down to General Ledger transactions, the drilldown view will look the same in all reports.
Icon | Description |
![]() |
Dimensions: These are dimensions from the ERP system, such as General Ledger, Sales, etc. |
![]() |
Fields: These are fields from the selected dimension, such as Account, Account Name, Status, etc. |
![]() |
Amounts |
3. (If you have access to more than one company.) From the Select company menu, select the company you want to edit the drilldown for.
4. Under Select dimension, select the module for which you want to edit the drilldown view. For example, if you want to customize the drilldown for reports on General Ledger transactions, click the General Ledger folder.
5. Under the module folder, select a dimension, such as, General Ledger Transactions.
Now, two panes open:
6. To start customizing the drilldown view, click the Customize button.
NOTE: When you click the button, you will see a new field in the Drilldown layout list; Field being drilled down. This is the field in the report where the end users click to drill down from. Usually, this will be an amount, such as Net Amount.
7. Edit the drilldown as you want:
8. Click Save.
In this example, we have a default drilldown view as shown in Figure 1.
In the figure, you can see how the default setup looks in the Drilldown layout editor, and in the drilldown view from a run report. As you can see, the order of the columns matches the order in the Drilldown layout section.
NOTE: The dimensions and fields may have different names in your ERP system.
Figure 1 Default drilldown view
We want to make the following changes to the drilldown layout for reports based on General Ledger Transactions.
We take the following steps:
5. Under Drilldown layout, next to Region, click Remove to remove the Region column from the layout.
6. Under Drilldown layout, move Net Amount after Description.
7. Under Available fields, open the Account folder and next to Status, click Add.
The Status column is added to the drilldown layout.
8. Click Save.
If we now run a report in Live Reporting, such as a Profit and Loss report, and drill down, we can see the following effects of the customizing in the figure below:
Drilldown before customizing
Drilldown after customizing
It is now possible to move content in OneStop Reporting from a user to another user. This ‘change ownership’ functionality can be useful for transferring content, for example, when a user is removed/deleted from a tenant in the portal. A typical situation where this functionality is applicable is when a user ends their employment and another user should inherit their work in the portal.
NOTE: You can only transfer content at the tenant level. Consequently, if the original user is a group user, you must move content from the user for each tenant in the group.
Examples of content that can be moved:
NOTE: There are a few things to consider when moving content: You need to make sure the receiving user has the appropriate licenses, roles, permissions and data accesses or the user might not see all the moved content. Also note that all history of reports and jobs will be removed. If you want to keep historic runs of a report, you need to first send it to the archive, before moving the content.
NOTE: If the user is a Group user, there will be no option to remove user, only to transfer content. The group user must be removed from the group level.
The Confirm remove user dialog box opens. You will see a list of content that exists on the user’s profile.
7. In the Move content and remove user dialog box, select the Move content before removing user checkbox.
8. (For cloud connections) Clear cloud data connection credentials checkbox.
NOTE: For both options described above, the receiving user will be able to see all companies that those connections have access to in the connected systems.
9. Under Move content to, select the user you want to transfer content to.
10. Click Next.
11. In the Confirm action dialog box, confirm the action by entering the name of the user being removed.
12. Click the Start moving button.
You can also move content to another user without removing the user.
NOTE: There are a few things to consider when moving content: You need to make sure the receiving user has the appropriate licenses, roles, permissions and data accesses or the user might not see all the moved content. Also note that all history of reports and jobs will be removed. If you want to keep historic runs of a report, you need to first send it to the archive, before moving the content.
7. (For cloud connections) In the Move content dialog box, Clear cloud data connection credentials checkbox.
NOTE: For both options described above, the receiving user will be able to see all companies that those connections have access to in the connected systems.
8. Under Move content to, select the user you want to transfer content to.
9. Click Next.
10. In the Confirm action dialog box, confirm the action by entering the name of the user being removed.
11. Click the Start moving button.
The receiving user will get an email from the system, informing that he or she has received content in OneStop Reporting.
NOTE: If the Clear cloud data connection credentials checkbox was selected when moving the content, all credentials for data connections to the cloud ERP system has been cleared. You must reauthenticate them to be able to import data.
Workflows, assignments, reviewers, approvers are moved. The moved workflows are shown with the name of the previous owner in the Moved from column.
The receiving user might get new assignments if the previous content owner had assignments in a moved workflow, such as reviewer or approver. The workflow card will then show the user the workflow assignment is moved from.
Users can now send reports as PDFs from Publisher.
NOTE: To get proper PDF formatting, check that the print area is set correctly in the report template. For more information, see Page setup for reports
On the Companies tab at the tenant level, administrators can now add information about the companies, such as company code, internal project number, or other free text information. Later, the information can be used when using the new reporting tool described below.
To add company information;
There is now a new Reports tab for administrators on the top level where they can create Company List and User List reports. Administrators can use information they have added to the Companies tab at the tenant level to create the Company List report.
Example of report exported to Excel
Administrators can now search for users and companies, in addition to the existing search for tenants.
NOTE: You must have access to at least two tenants to be able to see the Search box.
To search for users, companies, or tenants;
After several of customer requests, we are pleased to announce that we have finally implemented Visma Reporting History Customer and Supplier (‘historiske åpne poster’) logic. This means you can now create reports that retrieve open entries for Accounts Receivables and Payables back in time. In addition, we also have reports using this logic available in the Marketplace (in Norwegian). Subsequently, the previous historical factsets will be removed. Reports built with these will still run successfully; however, no new reports can be built on these factsets.
For our Norwegian customers, open entries report templates for Accounts Receivables and Payables, for customers and suppliers, are now available here. These reports are built on the new Visma Reporting History Customer and Supplier (‘historiske åpne poster’) logic we have implemented (see above).
We have created a new course in OneStop Reporting e-Learning. In this course, users learn how they can transfer content from one user to another.
We have created two new e-learning short videos for administrators:
Administrators at different levels: In this video, we show you what rights and accesses administrators at different levels have in OneStop Reporting. We look at how the administration page looks like for an administrator at the top level, the tenant level, and the group level. We will also go through rights and at which level they can manage users.
Limit users’ data access: In this video, you learn how you can limit the data access for a user.
In this course, we take a look at how the property hierarchy works for report definitions in Report Designer; that is, the relationship between sheet, row, column, and cell level.
Report Designer – Report Parameters: In this course, we take a look at how the report parameters work for report definitions in Report Designer. Users learn how Report Parameters is one of the components in OneStop Reporting that allows designers to create a dynamic report so that the same report template can be used for multiple reports with minimal adjustments. More specifically, users learn how to create new parameters, edit existing parameters, how they can be used to create sheet per value, and how to hide parameters and insert a default parameter value.
Version: v5.2.30109.0931
We have now enabled a Microsoft sign-in option for users when signing in to the OneStop Reporting portal.
Users can now choose to use their OneStop Reporting password, or click Sign in with Microsoft to use their Microsoft password.
NOTE: The first time you use Sign in with Microsoft, you must approve this as a sign-in method.
To be able to use AAD with the portal, you must register the portal as an app in your AAD tenant and retrieve the Application ID. See Microsoft documentation for more information.
Now, users can sign in to OneStop reporting using their Microsoft account.
If you want to enforce users to use Microsoft to sign in, see Require Azure Active Directory (AAD) sign-in for all users below.
Now all users are required to use their Microsoft account password to sign in to OneStop Reporting and can no longer use their OneStop Reporting password.
NOTE: If users have access to multiple tenants where one requires Microsoft sign-in and another does not, then they are required to sign in again when switching to the tenant that requires Microsoft sign-in.
When an administrator has entered a domain under Require Azure Active Directory (AAD) sign-in for the given domains, users will get a Sign in menu where they are asked to select a Microsoft account.
To enhance user security in OneStop Reporting, we have made it possible to use Multi-Factor Authentication (MFA) when signing in to the portal.
MFA is an enhanced security system that verifies a user’s identity by requiring two or more forms of authentication. Rather than just asking for a username and password, MFA requires additional credentials, such as a code from the user’s smartphone.
MFA is an effective way to provide increased security. Usernames and passwords can be stolen, and they have become increasingly susceptible to brute force attacks. MFA creates multiple layers of security to help increase the confidence that the user requesting access is actually who they claim to be.
With MFA, even if an attacker manages to learn the user’s username and password, it is useless without also having possession of the additional authentication method. In OneStop Reporting, MFA works by requiring two authentication methods:
An authenticator app is usually installed on a smartphone and you scan a barcode or enter a key to create an account. After the account is created, the authenticator app generates a 6-8 digit passcode every 30 seconds. The passcode can, for example, be used for login as an extra authentication method in addition to a username and password.
The passcodes are generated from a secret code that is shared between the service you are using, such as OneStop Reporting, and your device, as well as the current time.
Google Authenticator app example
There are a variety of authenticator apps you can download to your phone from Google Play and the IOS App Store, but we recommend that you use Google Authenticator or Microsoft Authenticator, as those are the ones we have fully tested our MFA solution on.
Authenticator apps in Google Play
For more information about installing and setting up an Authenticator app, see Install and set up an Authenticator app
In OneStop Reporting, users can set up MFA from their user settings. In addition, administrators can enforce an MFA policy for all end users. See the user procedures below for more information:
You have now set up MFA for your OneStop Reporting user profile. The next time you log in to OneStop Reporting portal, you must enter your username and password, and then enter a verification code from your authenticator app.
Click here for video on how to set up MFA on your account:
If you do not have a verification code, click the Do not have a code? link to read more about the MFA setup.
NOTE: You can click the More information link to read more about Multi-Factor Authentication (MFA).
Multi-Factor Authentication (MFA) policy is now enabled for this organization. All users must use MFA to sign into the underlying tenants and groups.
If your administrator has enabled a Multi-Factor Authentication (MFA) policy for your organization, you will receive a message:
Your organization’s security policy requires you to set up Multi-Factor Authentication (MFA) for your account.
You have now set up MFA for your OneStop Reporting user profile. The next time you log in to OneStop Reporting portal, you must enter your username and password, and then enter a verification code from your authentication app.
If you do not have a verification code, click the Do not have a code? link to read more about the MFA setup.
If enabled by an administrator, users can now use the Microsoft sign-in option when signing in to the OneStop Reporting portal.
Users can now choose to use their OneStop Reporting password, or click Sign in with Microsoft to use their Microsoft password.
Now, users can sign in to OneStop reporting using their Microsoft account.
* To be able to use AAD with the portal, you must register the portal as an app in your AAD tenant and retrieve the Application ID. See Microsoft documentation for more information.
Administrators can also require all users to use Microsoft to sign in. See Require Azure Active Directory (AAD) sign-in for all users below.
NOTE: To be able to use AAD sign-in, you must have enabled AAD in System Settings and entered the Application ID from Azure.
Now all users are required to use their Microsoft account password to sign in to OneStop Reporting and can no longer use their OneStop Reporting password.
NOTE: If users have access to multiple tenants where one requires Microsoft sign-in and another does not, then they are required to sign in again when switching to the tenant that requires Microsoft sign-in.
When an administrator has entered a domain under Require Azure Active Directory (AAD) sign-in for the given domains, users will get a Sign in menu where they are asked to select a Microsoft account.
We are now introducing a new Budgeting license. Users with this license will have the possibility to budget directly in the Budgeting module. In the past, users were required to have a license for Report Designer to have access to the Budgeting module, but this is no longer necessary.
In addition to budget directly in the portal, they can download budget templates from the Marketplace, and then download the budgets locally if they want. Furthermore, they can assign budget templates to other users and roles. NOTE: This license does not allow users to upload or create budget templates.
Users with the Budgeting license will also get access to the Assignments and Workflow modules.
If given the Can edit data from Data Manager permission, they also have access to Data Manager. For more information, see section below.
Users can now control access to Data Manager from Permissions in Administration.
To grant a user access to Data Manager;
We have added an option in Administration for Group Users, so that users can be added with full access permissions in all subtenants (data access, drilldown, etc.) without being administrators.
The three options for Group Users are now:
When existing users are added to a tenant, they are notified with information about the user that added them to the tenant.
Playlists in Archive are now sorted by date. In the past, users would see their unread playlists at the top of the list. We have changed this because most of our users are primarily interested in their most recent reports.
If you have ( ) selected a Category in Live Reporting or Budgeting, and select to upload, duplicate, create new, or download report/budget template(s) from the Marketplace, the report(s) is automatically added to the selected Category.
NOTE: You can select multiple categories to add report/budget templates to.
NOTE: Click here to learn more about managing categories in Live Reporting, or here to learn about managing categories in Budgeting.
The report templates are added to the Category/categories you have selected.
In the past, users had to press Ctrl/Shift to select multiple values in the parameter lookup. Now, users can click a value, then click again and scroll to select a range of values.
NOTE: This only applies to reports that allow multi-selection for parameters.
Some of our users have very large reports, containing numerous cells with formulas, many that are referring to other cells and functions. This might cause performance issues when running reports in the portal. Therefore, we have made it possible to run reports in “static mode”. This means that all formulas are removed in the workbook and the values are replaced with actual cell values.
Users can control the formula settings for a report template from the Report Properties in Report Designer. On the Reporting tab, there is now a Keep formulas in run report checkbox. If this checkbox is deselected, the formulas are removed from the report.
NOTE: This option will not have any impact on budgets.
All formulas in the generated report are kept during processing.
All formulas in the generated report are now removed during processing, and the values are replaced with actual cell values. When formulas are removed from a report, it is no longer possible to make calculations in run reports in Live Reporting.
When formulas are removed from the report template, the drilldown will function as normal.
NOTE: For reports that contain advanced formulas, such as IF and INDIRECT in the same formula or when referring to other sheets, it is safest to select the Keep formulas in run report checkbox to ensure the formulas work as intended in the portal.
In the past, users clicking the Help button in Report Designer would get the default language English. Now, users are redirected to the help in Norwegian, Danish or Swedish depending on their language settings.
Store even unchanged cells has changed name to Store unchanged cells. The logic remains the same: This option will force data from this cell to always be stored. The application will not do a check whether the input cell has changed its value or not.
Ignore cell value 0 has changed name to Delete transactions if cell value is 0, and will now have the following logic:
Suppress delete has changed name to Delete transactions for empty cells. The logic remains the same: If this option is selected, the value is used to update existing/insert a record in the storage dimension. This will also apply to transactions where there has been a value that has now been set to 0/blank/deleted.
It is now possible to download a budget as an Excel file from an assignment in Assignments. The Download functionality is available both for single assignments from Budgeting and assignments in a workflow.
In the past, there have been issues when using, for example, the Norwegian standard date format; day, textual month, and year. The issue has now been solved and the following setting can be used:
For this release, we have worked on improving the KPI and Expressions functionality in Report Designer. Specifically, we have implemented the following fixes:
We have fixed an issue where users have experienced that the grouping on the Grouping/Sorting tab would still be active even if they deselected the Expanding checkbox. This would cause the group to still expand. The issue is now fixed, so that when a user deselects the Expanding checkbox, the grouping is now automatically set to None.
Users can now expand columns in Line Item Details if they have large numbers that show a number sign, #, due to lack of space in the column.
In the past, some users have experienced that the language of their report changes to English when they export a report to pdf. This is now fixed, and reports will now have the same language as the user has set as their language.
We have fixed an issue where some users have experienced getting error messages when selecting parameters for their assignments (when the Let User Decide option is selected for parameters in Workflow).
Version: v5.2.20903.1420
For this release, we have focused on improving the Workflow and Assignments functionality. Above all, many of the improvements focus on functionality for collaboration across teams during the budgeting process.
To make it easier for users to know when there is a new assignment for them, they will now get a notification, either in Notifications or by email, with a direct link to their assignment. In addition, users can now see assignments that have a start date in the future in Assignments.
You can now keep everyone in a budgeting workflow in the loop by allowing reviewers and approvers to comment on all published workflows, at any time during the budgeting process. All comments will be visible in the Activity log. In addition, everyone with access to the workflow can see the Workflow status.
Furthermore, users can now see their completed assignments as these are now saved under a Completed section in the Assignments module. We have also made it easier to find budgets, by adding a Search box for both workflows and assignments.
Also new is the possibility to edit a budget template that is part of a workflow. Users can edit most aspects of the budget apart from changing the report parameters.
In the past, only the creator of the workflow could see the Workflow status. Now, all users who have access to the Workflow module and is a part of the workflow can see the workflow status overview.
To access the workflow status overview;
Users can now access their assignments directly from the Workflow status view.
When users are editing the User assignments, we have added a highlighting color so they can better see which templates and/or users are affected by the editing.
The dialog box for selecting templates in the workflow has been slightly changed to provide more functionality. For example, users can now see how many templates they have selected.
Now, when you create a new workflow, and click the Select companies button, you will get the Let user decide option at the top of the list of companies.
You can now see the user name of the assignee on the assignment cards.
Users will now get a notification, in the Notifications menu or by email, when there is an assignment for them, or any other activity in their assignments, such as comments. To access the assignment, the user can click on the notification or the Open link in the email, and they will be taken directly to the assignment.
The assignment notifications also apply to single assignments coming directly from the Budgeting module.
Assignments that have a start date in the future will now be visible for the user in the Assignment module, under Workflows. The user will not be able to start on the assignment until the specified start date and the Assignment card will be gray until the start date is reached.
A user’s completed assignments are now saved under a Completed section. The same applies for completed workflows; when an entire workflow is completed, it will be stored under a Completed work section. The completed workflows are sorted based on completed dates. Workflows in progress are sorted based on the date of the last activity on the workflow.
NOTE: The Completed section is collapsed by default. Click the arrow to expand the section.
To make it easier for users to get an overview of their assignments, we have added Collapse and Expand buttons for assignments.
The last selection the user makes, expanded or collapsed, remains the next time the user opens the assignment.
We have added a Search box for both workflows and assignments in the Assignments module.
It is now possible for the workflow creator to edit the date interval for a published workflow. The user can edit the date interval for the whole workflow, or for the various assignments in the assignments table.
NOTE: You cannot make any other edits to the workflow.
It is now possible to edit a budget template in a published workflow.
When you edit a budget template that is part of a workflow, you will receive the following message:
“This budget template is used in assignments or workflows. If you choose to edit this budget template, these assignments or workflows will be updated.
Please be aware that any changes you make may affect the budgeting process.
NOTE: Make sure you do not change any report parameters as this will prevent you from publishing your changes.”
To edit the budget template, click Edit anyway.
You can edit most aspects of the budget templates apart from report parameters. If you attempt to edit the report parameters, you will not be able to publish and must undo the edit.
To undo the edit;
After you have edited a budget template that is part of a workflow, the assignees must rerun any templates they have run before.
If they have the budget template open, they will receive a message from the system that the template is updated. If they run the template, they will lose any changes they have done since they last saved.
If a user’s assignment contains a Let user decide parameter, the user can now generate assignments several times. In the past, the Assignment card would disappear after generating an assignment, but now the card will remain in the Create assignments section allowing users to create different budgets for different parameters from the same assignment.
For example, if a user wants to create budgets for different projects, such as, Project A, Project B, etc., the user can create multiple assignments. The workflow’s Create assignments card will be available throughout the budgeting process, so the user can go back to create assignments for other parameters, as many as desired.
NOTE: If there is a time limit set on the workflow, the assignment card will be closed after the end date.
When a workflow is published, all participants in the workflow, including reviewers and approvers, can now see the assignments before they are submitted. In this way, reviewers and approvers can add and read comments to the budget before the budget user has submitted the assignments and sent for review/approval. This makes the Assignments module a more complete tool for the budgeting process.
In the example in the figure below, James is the reviewer in the workflow. As you can see, all of his assignments cards are gray, because the budget users have not started or finished their budgeting. He can, however, open all budgets in the assignments to read and write comments in the Activity log pane.
Some users have experienced problems with workflow statuses when going from reviewer to approver. The issue is now solved.
The period function, {PeriodCalc.CurrentPeriod}, is now a valid parameter value when assigning a budget.
We have now made it possible to change the language of the Help pages by selecting from the language buttons at the top of the Help pages.
The Help pages are available in Swedish, Norwegian, English, and Danish. Please note that we are currently working on updating the help for Swedish, Norwegian and Danish to reflect the latest releases of OneStop Reporting. The English help pages will always contain the most recent updates.
French is now available as a language in the OneStop Reporting Portal, as well as in Report Designer.
To change the language of the portal;
We have made the following change for user permissions:
Can manage connections has been moved out of Permissions. This means that if a user should be able to set up connections to retrieve data from the ERP system, this permission must be set separately.
We have added a new permission in the user settings to allow administrators to control whether a user should be allowed to download a report in Archive as an Excel file or not. If a user does not have this permission, the report can only be downloaded as a pdf.
This can be useful if there are parts of a report, such as hidden data, that you do not want other users to see.
We have now made it possible for users to make a connection private in Get Data > Create new connection/Edit connection. This can be very useful for users that have multiple companies in a connection and want to prevent users with the Can manage connections permission (see above) from editing the connection. Even if a connection is locked, the users with the Can manage connections permission will still see the connection, but it will be locked for editing.
NOTE: Administrators at the top level can still manage all connections, even locked connections made by other users.
When you first set up a connection, or if you click Edit on an existing connection, you will now see a Allow other users to edit this connection switch. The switch is off
by default.
IMPORTANT: If a connection is not private, users with the Can manage connections permission can see all companies in the connections, even companies they do not have data access to.
NOTE: All existing connections will be locked to the user who created the connection initially.
As mentioned above, the new lock connections option also affects how connections are displayed in the Get Data > Connections list.
In the past, the Connections list was filtered, for example, according to which companies users had data access to. Now, we have changed this, and users with the Can manage connections permission will see all connections that exist in a tenant, even connections they cannot edit (that are locked ). If a connection has the Allow other users to edit this connection switch turned on, users that are allowed to manage connections will also see companies they do not have data access to.
NOTE: Now that users with the Can manage connections permission can see all connections, they can also see all Connection names. Users creating connections should therefore be careful when they select connection names.
We no longer support Microsoft Office versions lower than 2013.
There is a change in how the Sheet per value functionality works.
Now, in order for this to work, you must have the value, for example, Region, on the Sheet filter.
To create Sheet per value;
4. In the Report Parameter Wizard, click Next, and then Next again.
5. Under Options, select the Create sheet per value checkbox.
6. Click Finish.
This checkbox is selected by default to protect non-input cells in budget templates. This means, when the checkbox is selected end users cannot input numbers to any cells in the Budgeting module, apart from those that contain storage rules (budgeting amounts with storage rules defined). However, you now have the option of deselecting this checkbox. When this is deselected, end users can input numbers into any cell in the budget template, also those that do not contain any storage rules. Please note that this option will apply to the whole budget and make any cell an editable cell.
To access the Protect non-input cells checkbox;
You can now access the help for Report Designer directly from a Help button on the OneStop Reporting ribbon.
Store even unchanged cells option has changed name to Store unchanged cells. The logic remains the same: This option will force data from this cell to always be stored. The application will not do a check whether the input cell has changed its value or not.
Ignore cell value 0 option has changed name to Delete transactions if cell value is 0, and will now have the following logic:
Suppress delete option has changed name to Delete transactions for empty cells. The logic remains the same: If this option is selected, the value is used to update existing/insert a record in the storage dimension. This will also apply to transactions where there has been a value that has now been set to 0.
In the past, some users have experienced problems when they have a non-OSR Excel workbook and Report Designer open at the same time. The issue is now solved.
We have fixed an issue where users have experienced being asked to log in again when switching company in Report Designer. Users should not have to log in again after switching company.
We have fixed an error where users who already had Report Designer installed were asked to download Report Designer each time they opened a report from the portal.
Some customers have experienced that reports with the Year to Date function in a row or column would not show any numbers. The issue has been fixed and all reports containing this function should now behave as normal.
In the past, users have experienced that administrator users in a role do not have all permissions set by default. This issue has now been fixed.
Users will now get a Confirm action dialog box if they leave or refresh the Data Manager without saving their work.
We have made it possible to use comma as a decimal separator in Data Manager when users have selected a portal language in which comma as a decimal separator is the standard. In the past, Data Manager would disregard commas as a decimal separator and, for example, change 0,1 to 1 when numbers were saved.
Some users have experienced that the Vertical/Horizontal toggle button has disappeared when they open multiple reports in Archive. The issue has now been fixed.
In the past, if OneStop Reporting detected an error in the budget, such as a wrong character, and the user clicked Store, the budget would automatically refresh and, consequently, remove added budget numbers.
We have now fixed this issue, and the screen will not refresh. The user will now get the error message, but the added numbers will not disappear.
Some users have experienced an error when a budget template is in Draft mode as they run the report and try to use the Lookup for the parameter. This issue has now been fixed.
Some customers have experienced that when they try to copy and paste numbers with decimals, the numbers are rounded up or down to the nearest whole number. We have now fixed this issue and decimals are kept when users are copying and pasting numbers in their budgets. In addition, users can copy numbers with decimals from Excel to budgets in the portal.
In some cases, users who have the OneStop Reporting portal language set to Norwegian have experienced issues when storing budget numbers with decimals. The application would remove the decimal numbers. This issue is fixed and decimals are now saved to the budget.
Some users have experienced that groups disappear from the Layout Editor when designing reports in Report Designer. To fix this issue it is recommended to turn on the Optimize for compatibility option;
Please note that you must restart the application for the change to take effect.
Version: v5.2.20430.1215
Download the latest version here.
We have made some changes to Administration to accommodate larger accounting firms that use Groups to organize their clients.
We have developed a new Search users functionality, where you can search for users and get information about the user, such as email address, which tenants and/or groups they belong to, and if they have administrator rights.
To search for a user;
NOTE: If you see a Key icon next to the tenant or group, that means the user has administrator rights in that group or tenant.
We have also made some changes to the Group level.
For larger organizations, such as accounting firms, it can be useful to organize the tenants into groups. In this way, it is easier for an administrator to add a user to multiple tenants, and giving them permissions and data accesses.
For the Group level , you now see the tabs shown in the figure:
Tab | Description | |
1 |
Overview |
Shows the group name. Click ![]() |
2 |
Group users |
Shows users that have access to the group level. You can add or remove group users. These users will have access to all tenants in the group and will automatically get access to manage other subgroups and tenants within the hierarchy. |
3 |
Licensing |
Allocate licenses for users at the group level.
NOTE: If you do not have a shared license, you will not see this tab. |
A group user is a user who can access all tenants in a group.
NOTE: If you want to grant a user Group Administrator rights, turn on the Group Administrator switch. A Group Administrator can manage group users, and create new tenants and subgroups. In addition, they can manage licenses at the group level.
NOTE: If you want to grant a user all permissions for all tenant in the group, turn on the All tenant permission switch. This permission gives the user administrator rights for all tenants in the group. In this way, they can manage licenses, users, and roles at the tenant level.
NOTE: Licenses for group users is managed from here and not at the tenant level. At the tenant level, the module accesses will be locked when a user is a group user.
NOTE: You can see how many available licenses you have in the column headers.
To see an example on how you can use the Group level, see Organize tenants in groups: An example.
Because you now can add users to a tenant by adding them at the Group level, there are some changes to the permissions, data and module access settings on the Users tab at the Tenant level.
If a user is a Group User, he or she will have a Lock icon next to their names on the Users tab. If the user is given All tenant permissions at the Group level, or is a Group Administrator, their permissions and data access is inherited from the Group level and cannot be managed from the Tenant level.
Module access is always given at the Group level for Group Users.
You can now use drag-and-drop to organize the tenants in your groups in the tree structure. You can, for example, move your tenants from one group to another. In addition, you can have a tenant in multiple groups if you want. When you move or add a tenant to a group, the group users are automatically added to the tenant you add or move.
NOTE: This functionality is only available for users with shared licenses.
To move a tenant to another group;
The group users in the destination group will automatically be added as tenant users.
NOTE: If you move a tenant from one group to another, the group users from the original group are removed from the tenant.
In the example in the figure, we move the Financely tenant under the Team William group to the Team Noora group. All group users from Team William are removed and the group users in Team Noora will be added.
To add a tenant to another group, while keeping the tenant in the original group;
You will now have the tenant in both groups.
The group users will automatically be added as tenant users.
In the example in the figure, we add the Financely tenant under the Team William group to the Team Noora group. In this way, we have the Financely tenant under both the Team William group and the Team Noora group. The group users for Team Noora will be added, and the group users for Team William are kept.
We have changed the Add tenants dialog box, so it does not close for each tenant you add. In the past, the dialog box would close when you clicked the Create button. Now, the dialog box stays open so you can add multiple tenants until you click the Close button.
We have added a Search users functionality to the Tenant level in Administration that allows you to only search for users in that particular tenant.
To search for a user;
It is now possible to create your own Marketplace for report templates. This is a feature we mainly offer to accounting firms as it requires OneStop Reporting to set up a separate tenant for this purpose. When you have a Marketplace tenant, you can upload templates to this marketplace and share between your tenants. The users in the other tenants will then only see the report templates you have shared when they click Get templates in Live Reporting or Budgeting. Please contact support.osr@visma.com if you want to set up a Marketplace tenant.
We have fixed an issue where Publisher jobs would run at incorrect times if the server time differed from UTC-time.
We have changed the dialog box for deleting companies from a tenant in Administration to be more informative. The change has been implemented to make users aware of what happens when they delete a company.
In Live Reporting, if the parameter is a date picker, today’s date is now automatically set.
We have added a Search for companies field when users create a new or edit an existing connection in the Get Data module.
We have improved the validation process for data connections. In this way, users will get more detailed error messages with information about the cause of the error.
In the past, customers have experienced that the OSR services do not start automatically after server reboot. This would cause reports not being run until the services were manually started again. We have solved this by setting the services to Automatic (Delayed Start) in the installer.
We have improved the Active Directory validation process.
To add Active Directory users to OneStop Reporting, see Active Directory.
(On-Premise)
OneStop Reporting offers an online training platform – eLearning. The platform contains educational courses and videos, so that you can get a unique insight into the OneStop Reporting solutions.
To order eLearning, please contact us at orders@onestopreporting.com.
You can learn whenever you want, and wherever it suits you. This gives you the opportunity to learn at your own pace, and always have access to educational material.
For more information about the e-learning, click here.
We have improved our context-sensitive help section, so that our customers see relevant help topics. In the past, we were not able to differentiate between the various installations of the OneStop Reporting portal. With the upgrade, users will get help specially tailored for their system.
To open the Help pane;
To open the Help in the browser;
The OneStop Reporting portal has now been translated into Swedish and Danish.
To change the language of the portal;
In Live Reporting, when you open a report template, you can use the slider to select to refresh data every 5, 10, 15, 30, or 60 minutes.
You can now download executed reports or report packages as a PDF file.
We have made the Report parameters sections collapsible so users get more space when working on report and budgets in Live Reporting, Budgeting and Assignments.
To hide the Report parameters sections;
You can now schedule a publishing job to recur every 7 days (in addition to the monthly scheduling).
__________________________________________________
To use the Budgeting setup in OneStop Reporting, the user must have the Can manage connections permission and a Budgeting license.
In the past users had to be Customer Administrators to use the Budgeting setup.
In the installation wizard, you can install Voucher Service.
In the Voucher Service step, you must enter port number for the voucher service. This is the port that is used for communicating to the external web server.
To turn on the Voucher Service;
NOTE: If you have already set up the voucher service, you can use this user interface to edit the voucher service URL.
We have now support integration extensions. Please note that we currently do not have any tools for you to build extensions in OneStop Reporting, but you can upload extensions and use.
As an administrator of a tenant, take the following steps to upload a customized model or an extension:
NOTE: Models can only be uploaded if the model is licensed. Extensions can only be uploaded if the base model is installed and licensed.
To remove an extension;
In the past, administrators could remove themselves as administrators, even when they were the only administrator at that level. We have now removed this functionality to prevent the risk of not having administrator rights on this level.
If you try to remove the last Administrator at the Customer level, you will receive this message: “There has to be at least one Customer Administrator. Assign another user as Administrator before removing this user.” You must then add another Administrator and try again.
We now offer partially support for macros (Excel) for reports in OneStop Reporting.
You can use macros in your reports when you create them in Report Designer and upload to OneStop Reporting portal. However, the macros will not run in the portal, but must be downloaded to Excel by the user for the macros to take effect.
5. In the Save as dialog box, select the Excel Macro-Enabled Workbook (*.xlsm) file format and click Save.
The report is uploaded to the portal.
NOTE: The macros cannot be run in Live Reporting, so the receiver of the report must download the report to Excel.
You cannot use Excel Macro-Enabled Workbook for packages in OneStop Reporting; the macros will only work for the first report in the package.
In addition, you cannot use the Sheet per value functionality when using macros in your report.
We have implemented a new Settings menu for conditional storage for when creating budget templates in Report Designer.
Previously this options only had a Store always option. Now, users can better control how data are stored, for example, by ignoring rows or columns.
Store even unchanged cells: This option will force data from this cell to always be stored. The application will not do a check whether the input cell has changed its value or not.
Ignoring rows or columns:
Ignore cell value 0: Means that cells including 0, NULL, or empty are not stored. This is useful when you have larger budgets to avoid creating unnecessary records.
Suppress delete: Normally, values in a cell are deleted after pressing BACKSPACE or DEL or blanking out the value. If this option is selected, the value is used to update existing/insert a record in the storage dimension.
We now support Visma Lønn, Visma Administration and Microsoft Dynamics AX (2009).
The upgrade will fix a number of issues, such as:
For more information, see: https://www.spreadsheetgear.com/downloads/whatsnew.aspx
In the previous version, users could not set a dynamic path for Visma Document Center. This has now been fixed.
If you, for example, enter \\visma1\VismaData\Workflow\{Company}\Documents2 this path will now point to \\visma1\VismaData\Workflow\F0014\Documents2. (Where F0014 is the company code.)
For Visma Business, you can use the Prog table to override the path;
If you set up a key named voucherviewer, the Data area column should include an exact path to the vouchers, including the company code, such as, C:\Visma\Vouchers\F4100\Documents.
For outgoing invoices:
For incoming invoices:
(Screen shots are in from a Norwegian user interface)
For Visma Global, you can override the path from the [<schema>].[PMValue] table. The key is called “documents” and the column ValueText determines the path.
We have now implemented PDF support for Visma Document Center, so users can view vouchers from pdf format.
Voucher viewer fails when customers have multiple companies. We have fixed this bug, but for users who have already installed, you can use the following workaround:
If you have more than one company, you must update the path for the vouchers in the ValueText field in the PMValue table where the Name column is Documents.
You must do this for each company database.
Data Manager: We have fixed an issue where users could not delete rows in the Data Manager table. The Delete rows button is now available for Visma Global.
Fixed Norwegian User Interface issue: Some users have experienced getting Danish language when they selected Norwegian. If the problem persists after upgrading to the latest version of OneStop Reporting, please contact support.
AX Virtual Companies: We have made it possible for customers to use virtual companies and accounts in OneStop Reporting. The setup works exactly like it did in version 4.6, where users have to retrieve the folder location from the setting named Settings.ContentFolder. Then, a sub-folder path Models should be added to this path. The resulting path will be something like C:\OneStop\Content\Models.
For more information, see https://help.onestopreporting.com/help/misc/virtual-company-in-microsoft-dynamics-ax/?type=onpremise
Administration: Leading and trailing blanks in ERP connections: Some users have experienced formatting issues with report templates due to not being able to remove leading and trailing blanks when connecting to their ERP system. This issue is fixed by setting remove blanks as the default settings when connecting to the ERP system.