Deepak Dixit

Actual Result: AP vendor invoice journals and purchase orders do not display project stage data in the project drop-down selection.

Expected Result: Customer's expectation is to display project stage data in project drop down in AP vendor invoice journals and PO.

Currently as per design, it can be achieved with 2 lines. Let's say we've posted an intercompany transaction between USMF and USSI. In USSI, we have a balance of 100.00 debit for Intercompany receivable account 123. In USMF, we have a balance of 100.00 credit for Intercompany payable account 999. In the elimination rule, we would create two entries. One to eliminate 123 and a second line to eliminate 999 in the consolidation company. This would create a journal with a credit to 123 and a debit for 999. This would bring the balances of the entries to 0.00.

The Idea is like to see a single journal line that contains both the account and offset account information, representing both sides of the debit and credit, (Similar to general journal) while creating the elimination proposal.

Issue Description:

1. The Customer has a custom view on my 'On-Hand' form (Inventory Management->Enquiries and reports->On-hand list), the field list is different when inserting a column to the grid.
2. When customer create a new view on the form - call it 'My view - on hand' and remove some fields then save the view and pin it as the default view for the on hand form, after refreshing the browser, if attempt to insert a new column to the grid, get a different list of fields compared to when the standard view is the default view for the form. The difference in the list is significant.

Expected Result:

When having a custom view as the default view, the field that can be inserted into the grid does not match the field of the data source that is on the form. To get the full list of the fields back, the user must set the default view back to the standard view then customize their view in order to add any additional field that is not displayed. All fields for all data sources on a form should always be available to insert into the grid.

Let’s assume for any customer named X, total loyalty points= 10,000.

Customer X has silver membership and 1 loyalty point= 1AED, hence equivalent amount for 10,000 loyalty points=10,000 AED.

Expected Result:

1. 10,000 AED (Total amount available equivalent to loyalty points) balance should be reflected at POS or at backend.
2. If customer is using pay by loyalty points, it is reflecting the amount equivalent to price of the item against the loyalty points, but it doesn’t provide the information regarding total amount available equivalent to loyalty points with the customer so that customer can redeem and make payment against the loyalty points.

Actual Result:  The changed value should be reflecting on the order event page, but no data is available on this page.

Expected Result: The transactions for which the values have been changed should reflect on the order event page.