When I enter a NeedBy date at the header level - the ShipBy date autopopulates - this is okay.
When I enter an order line the dates at the line level take on the same values as the header - this is okay.
If we change a line to have a different NeedBy date at line level then save the change.
Then change the NeedBy date at header level - a pop up is displayed:
Bug - all dates at the line level are changed not only the ones that matched the previous NeedBy date.
I am testing version 2024.2.9.
Has anyone else seen this or reported it as a bug?
This is correct. If you change the header, which is just a default, then no lines are changed. They added the message to say, “Hey, I see you changed the header, do you want me to change all of the lines?” If you say yes, it does just that, otherwise your lines stay the same. Any new lines will default to the header values.
It sounds like a bug based on the verbiage. I would enter a ticket and see what they say. They might end up saying it is working as intended and the pop-up is wrong.
It seems like a nice feature TBH. Do users really want to manually change 20 lines one by one? Is it the awkward wording that we don’t like? Those fields on the header literally have no value other than default. Maybe the labels should be changed. This feature has been around since Vantage 8.
Specifies the date by which the customer needs to receive the order. The need by date on the order header is used as the default need by date for all the order lines. This date is also printed on the Sales Acknowledgment. If you need, click the Down Arrow and select a different date from the calendar. Show Me
If you change the Need By date on the Summary or Header sheet for an existing order, a message displays asking if you want to apply the date change to existing lines and releases.
If you select No, no line or release Need By dates change.
If you select Yes, the Need By date changes on all lines and releases whose Need By date match the previous order Need By date (the previously saved date).
Note: If you select to apply a new Need By date to all lines and releases, and a line or release has a different Need By date than the existing order header Need By date, the Need By date on the line or release does not change.
Note: If the Need By date in the Summary or Header sheet is blank but there are lines or releases with a specified Need By date, if you select a Need By date on the Summary or Header sheet and answer Yes to confirm the change, all lines and releases update with the header Need By date. All existing Need By dates on the order lines and releases are overwritten.
Important: This field is disabled if this order is a counter sale.
From the KINETIC Field Help
Specifies the date by which the customer needs to receive the order. The need by date on the order header is used as the default need by date for all the order lines. This date is also printed on the Sales Acknowledgment. If you need, click the Down Arrow and select a different date from the calendar (for example, 09/08/14). If you change the Need By date on the Summary or Header sheet for an existing order, a message displays asking if you want to apply the date change to existing lines and releases. If you select No, no line or release Need By dates change. If you select Yes, the Need By date changes on all lines and releases whose Need By date match the previous order Need By date (the previously saved date). If you select to apply a new Need By date to all lines and releases, and a line or release has a different Need By date than the existing order header Need By date, the Need By date on the line or release does not change. If the Need By date in the Summary or Header sheet is blank but there are lines or releases with a specified Need By date, if you select a Need By date on the Summary or Header sheet and answer Yes to confirm the change, all lines and releases update with the header Need By date. All existing Need By dates on the order lines and releases are overwritten.
It’s a bug.
The help describes how it is meant to behave:
“If you select Yes, the Need By date changes on all lines and releases whose Need By date match the previous order Need By date (the previously saved date).”
But in 2024.2.9 - all lines change regardless.
I’ve reported to Epicor as a bug and quite a significant one.
@Mark_Wonsil
Hi Mark,
I think this is a bug - the question offers to change the dates on lines that match - but all dates change regardless.
I’ve reported to Epicor as a bug.
I’ve always assumed all lines were updated. So the expected behavior we would be to find the lines that matched the previous value and only update those? How would one change all lines? All new lines would still use this as the default though?
Yes - the intended behaviour is to find all lines that matched the previous dates then change only those lines.
That functionality works pre 2024.2.9 but is broken in that version.
My live enviornment is 2022.2.10 and the functionality works as designed.
I might enter an Epicor Idea to suggest the prompt dialog that has three buttons:
Change matching
Change All
Cancel
I know I’ve seen where we had to change all the lines to one date and doing by matching would be the same as doing it one by one. I can see the need for doing it both ways.
Support have advised the bug is fixed in 2024.2.15 - they have suggested the fix is to install upto this patch.
Here is my dilemma.
I am working at 2 sites both of which are on 2022.2.10.
I have created test environments at versions 2024.2.2, 2024.2.5, 2024.2.6, 2024.2.8 and my current version 2024.2.9.
At each version I have encountered at least one significant conversion fail and/or significant bug.
The amount of time it is taking to test all of these versions has resulted in me delaying my upgrade process on numerous occassions.
What would everyone do in this scenario:
Proceed on 2024.2.9 with the bug and write a BPM to ‘workaround’ (everything else I have tested is working)
or
Upgrade to 2024.2.15 and start the testing process again fully
or
Upgrade to 2024.2.15 and perform a much lighter testing strategy
This feature has been around since Vantage 8.