Microsoft product team need to be really fast in action, in order to provide such useful features in time. Couple of ISVs and renouned developers do have design / code ready with them to review and incorporate in the product. Sometimes, its better to take a decision by focusing and considering the value of features, rather than going by the vote count.


Continued Comment Part III.....

If user creates new delivery address in the PO (header), then system shows that address in the Organization >> Entity >> Address list which is not correct. Organization can request a vendor to deliver the item at specific location, say other vendor site, for outsourcing or project work etc. This type of transaction can also be covered if another type of warehouse (Outsourcing) is used in the delivery address.


Continued Comment Part II.....

UI should have a capability of assigning a user, users or user group to one or multiple warehouses along with the below type of access rights-

a) No access - Warehouse won't be visible to the user anywhere in the transaction / inquire / report
b) Read only access - User will be able to use the warehouse to see the stock , inquiry, report or while transferring the item to "To" warehouse)
c) Full access - User will be able to use that warehouse in the transaction including "From" and "To" warehouse, can see all the transactions of that warehouse, inquiry and report.

I would suggest to provide list of menu items that user can use for the assigned warehouses. Existing security model is time consuming and complex. But this type of UI for user access can give a clear visibility stating which user will have access to which warehouse and related transactions/inquiry/report.

One more type of warehouse is needed as "Outsourcing". All the material sent out for any processing / repairs / replacement or service work (including office items like laptop etc.) should be routed through this type of warehouse, so that, a tracking can be done realizing which item is lying at which vendor, since how many days. If item is returned back then how much was paid for service charges or to repair the item. If item is changed after proess, then consumption of sent item and receipt of received item qty, cost etc should be tracked. A simple inward entry should be possible by taking the item as it is or by changing the item code or as a type service. If original form of the item is changed then consumption entry should be made and another item, if received, should be accepted in the store.

Currently, user need to define BOM mentioning vendor, service item or inventory item in it and then it can be used to send out for processing. Even if BOM related module is not implemented, this step is necessary.


Comment Part I.........

An organization can have multiple operating offices / sites / warehouses. When a user at that specific address creates any PO or SO or any other record, system populates only one default warehouse or location that is setup in the system. In the system, we need to create multiple virtual warehouses against one real warehouse of the organization in real world (e.g.in transit warehouse, wip, main, quarantine, packing, vendor outsourcing etc). This becomes troublesome everywhere. User can select wrong warehouse or wrong office (in case of non-inventory transactions). Making correction is another task user need to perform. The expectation here is, if Microsoft provides a way to give office/warehouse/site specific user access and default value in it, then it would be of the great help to the user and organization.

A simple user interface having tree structure in it can be provided as under. Below is only the example to create a tree structure.

A) Office One-
a) Site - A
i) Warehouse - I (Raw Material / Main storage)
ii) Warehouse - II (Production Warehouse)
iii) Warehouse - III (In Transit Warehouse)
iv) Warehouse - IV (Quarantine Warehouse)
List of other warehouses created under Site - A

b) Site - B
i) Warehouse - V (Finished Goods Warehouse)
ii) Warehouse - VI (In Transit Warehouse)

B) Office Two -
a) Site - C
i) Warehouse - VII (Raw Material / Main storage)
ii) Warehouse - VIII (Production Warehouse)
iii) Warehouse - IX (In Transit Warehouse)
List of other warehouses created under Site - C

b) Site - D
i) Warehouse - IV

C) Office Three - No Site - No Warehouse


This is important for the proper approval to maintain the vendor bank data.


1 customer raised as below
a. Export order created
b. packing slip is booked . At this time itself GST to be booked and e-invoice should be generated so that the shipped items can go from factory premises to port- this is really important as now before moving the goods the invoice number should be loaded on E- portal and once we give the invoice number we cannot change that and hence we cannot have commercial invoice
c. After shipping bill is posted then actual sales should be recognized


This same suggestion has come up in our environment as well.
Melissa had a good point that when the call window follows the technician, sometimes it runs into their hand and they will intermittently press a button, usually it is the hang-up button.

A good addition would be a voice command to hide the call window, such as "Remote Assist -> Show Call" and "Remote Assist -> Hide Call"

Other remote assist software has explored this option in the past and it would be a great addition.


Where can I read more about this? In my environment mapping to Contact or Lead is a must.


This would be nice. I'd note it's theoretically less important now that all tables have `SystemId` identifying each record/row, so that can be used in links. True, one then still has to hard-code the table number to filter in the target as a `const`, wihch is error-prone due to not showing the table name and susceptible to copy-paste-os.... and, of course, the target table might only have a RecordId of the related record, and adding/using TableNo and SystemId instead may be a lot of work or even breaking. So allowing to use current RecordId would be a welcome alternative