Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
Agreed with this idea. Our users are already concerned about the need to add key OOTB columns manually for each project (namely the Effort column), and the ability to add custom attributes and configure the grid to show them by default would definitely improve our users' experience.
There would need to be some mechanisms in place to highlight prices that have not been 'activated' in store, for HQ employees to chase etc. Otherwise, we will end up with a mismatch of pricing between stores and items selling at margins different than anticipated by the merchandising teams.
This solution doesn't fully solve the problem;
1. There may be multiple facings in the store that need to be updated
2. Some products may be individually price marked as opposed to shelf labelling
3. If monitoring is in place on the store to ensure they 'process price activations' in a timely period - it could be open to abuse, (i.e. Manager just scans all the new labels and doesn't actually affix, in order to stop head office chasing - which defeats the point of the enhancement).
Additionally, it could lead to more confusion in store - when the associate scans the item and the customer says - I saw it online / in another store / in a catalogue or advert, for a different price - how do they validate the price the system is showing them is actually wrong caused because they haven't activated it locally, and work out what it should be.
Personally - I feel if investment is to be made in this area - it should first focus on the difficulties in us being able to identify price changes as/before they happen in store (i.e. something in POS or HHT where I can list price changes which have not yet had new labels printed, scheduled to go live tomorrow - to then be able to determine what actions need to be taken - could possibly tie into task management?).
How to determine the correct action - Some of this is possible already, but need to be able to identify how many facings, which products are individually marked etc.
And then how to physically print the labels to a label printer. Which has been number 1 on ideas, since we were on Customer Voice!! https://experience.dynamics.com/ideas/idea/?ideaid=85d69b7a-5eaf-e711-80c0-00155d7cd0b4
In my opinion it is a functionality that has been lost. This option was in previous versions of Dynamics NAV. In fact, when the elements of the page are inspected, the filter does appear, it just isn't shown in the page.
We have several customers demanding this feature and this is a core requirement for multinational companies.
Still under review... Is this really on the roadmap?
Start with dark mode.
An ERP system is the most used system for many in the organisation.
All these Microsoft products have dark mode:
Yes! It would also be nice if we could choose that the default value is Yes instead of No
We are in the first phase of our implementation project to move from NAV 2013 to BC SaaS and are just now working on the Canadian EFT setup with our partner. During our testing we have discovered that the OOB data exchange definition which is supposed to be for Royal Bank of Canada (RBC) does not actually follow the RBC ACH specification for some fields as per the document posted on their website (https://www.rbcroyalbank.com/ach/file-451772.pdf). The exported file uses a Julian date with two-digit year, but the RBC spec requires a four-digit year (I confirmed this with our account manager at RBC). There are also several fields which RBC requires to be populated for payments destined to US-based banks, and the OOB file contains blanks for these fields. While confirming with our account manager these differences, they also noted that if a customer submits a file with any errors which result in the file being rejected, the bank will charge a service fee. This has real-world financial implications for customers who do not realize these discrepancies exist in the 'RBC compatible' OOB data exchange definition and attempt to use it as-is.
In the context of a large organization (e.g. provincial public service with multiple ministries and agencies that only has one tenant) it would be detrimental if a global admin had ability to delete/rename/share projects. These have to be managed at a lower level - environment admin. Otherwise, a single sloppy action by someone who is not familiar with specifics of each survey and business needs behind it can cause chaos.