on
RE:
I've found out that the fields
105; Shipping Agent Code ;Code10;TableRelation="Shipping Agent"
5794; Shipping Agent Service Code;Code10 ;TableRelation="Shipping Agent Services".Code
Are not present into the table 6650 "Return Shipment Header". BC should bring these fields over from the Sales Order.
RE:
This is about availability of those URLs embedded into notification e-mails generated from NAV/Business Central.
If I use Notification Method = Email with Display Target = Windows in Notification Setup, I get URL targeting the object with link to Windows client with specific "protocol" (dynamicsnav://...). This kind of link is also present in the end of e-mail referring to setups.
If I use desktop version of Outlook I can open these kind of links after confirmation in security notification which come out when you click on this URL. This opens Business Central application as expected.
However, if I try to open the same notification e-mail from web version of Outlook from Office365 portal, these links are disabled and not clickable (looks like hyperlinks get removed).
Similar thing happens if we open email in mobile email clients (mobile Outlook for Android or GMail app) and similar happens to URLs to mobile Business Central application. If we do a modification and put URLs with target to mobile Business Central application into same notification e-mails (as ms-dynamicsnav://...) they are also blocked by e-mail clients and are not operational. This is relevant for both desktops (windows) and mobile (at least for Android) platforms.
The idea is to make those links operational for all e-mail clients. If that is driven by certain security requirements or setups (either for e-mail clients or operating system), would be good that corresponding exceptions are put for restrictions during Business Central application installation.
RE:
When raising a purchase invoice and using the get receipt lines function, if the invoice is posted in error - the "cancel" and "correct" options are disabled and the only option is to raise a corrective credit memo. When this is done the "invoiced value" on the posted purchase receipt is not cleared, which distorts the "Receipt not invoiced" value. The receipt can also not be applied to the new invoice. I would like to suggest two changes:
1. Enable the cancel/correction functions for this scenario.
2. If a credit memo is applied to a posted invoice, then the invoiced value on the receipt should be the net of the invoice value and the credit memo.