B1UP Calendar dates by document lines
Respondida
When creating a calendar through B1Up the date is currently only managed at header level for a marketing document and not at row level. A Purchase Order for example may may many line with different ship dates for each line. You can create a calendar that shows the lines on the different dates but if you drag one of the entries to another date it changes the document header due date and not the ship date of the line. Can we have this changed to work or line level as well please. So if I have 4 lines on a PO with 2 different ship dates (2 lines per date) then 2 calendar entries would be created. When I then dragged an entry to a different date on the calendar all the lines that matched the original date would be changed to the new date. This should also apply to start and end times with these being managed at line level as well.
-
Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
(Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
Read more about the Feature Request process here
[Internal Id: 53177] -
Hi Paul, I like the idea and technically it should be possible except for 1 thing. You mention that you have 4 line with two different shipdate and you expect only 2 calendar entries. I can see that as an option as each of the calendar entries would need the secondary LineId fields as secondary primary key for this to be updateable in the DI-API. So I can only see this working if 4 separate calendar entries where to be shown (but on same day if ship date is the same)... The issue with basing the move on the date and not the LineId would be that is less flexible (what if only one of the two lines with same date is delayed/come early) and could run into issues with partial delivered and closed lines
Would this still be relevant with such a "limitation"
-
Hi Rasmus, thank you for your reply. I certainly see this as a requirement at line level and understand your logic but unfortunately in the current scenario I have the customer would not want to see a single calendar entry per line as they could have many lines for the same date on a single document i.e. 20 lines split across 3 dates, and it would make the calendar unreadable with 20 different entries as opposed to just 3. With regards to the case where a number of lines were grouped by date and the date of a single line were to change then I think it would be expected that this change would be made in the document itself and a refresh of the calendar would then produce a second entry. I hope I make sense.
Paul
-
Hi Paul
Thanks for explaining. While I understand, this is a highly customer-specific scenario with dates being the grouping. Others might want the ship-dates grouped by sales employee, item code, or some UDF even... That would essentially lead to us needing to give an option in the calendar source per every grouped field and doing a bunch of assumptions about what that grouping meant (again in relation to partial deliveries and closed lines). If it was all line by line any scenario would work with a single easy-to-understand system.
So I understand that is not what you want, but I fear your request is too niche to bring the right value to everyone... But let see if other comments and votes disprove that assumption
-
I have a customer requesting the calendar change the due date of the line on a purchase order. I am fine with an entry in the calendar for each purchase order row.
-
Hi Rasmus,
Thanks for your response. I understand what you are saying about the different possible requirements but as we are talking about calendar function and hence dates would it not be logical to consolidate by due date by default.
Regards
Paul
Iniciar sesión para dejar un comentario.
Comentarios
6 comentarios