This commit is contained in:
2021-02-18 23:05:07 +00:00
parent c2a294db70
commit 04b06a7243
2 changed files with 28 additions and 6 deletions

View File

@@ -106,10 +106,12 @@ todo: how to add locale keys in future after release without erasing all data?
CURRENTLY DOING: PurchaseOrder
Question: part number and part name, why both, it's fucking up the UI?
Can we settle on one only, it's confusing and weird
Yes, NUMBER is the only required in v7 sb required in v8 as well
name is for picklists not grid lists inside po form
todo: tax values and totals need to be calced at server and returned with record
put totals in PO header class as nonmapped fields and can calc at server
any update to items or anything really roundtrips to server and back with updated object returned which differs from other objects so need to acct for that.
todo: dynamically hide worequest columns if found to not be included
todo: maybe also insert a showwarehouses return nonmapped value with po and remove the fetch if can just hide column headers anyway
PO UI for items:
Use ops-backup form list of backups as concept, it uses a v-data-table

View File

@@ -857,17 +857,35 @@ async function createTableHeaders(vm) {
if (vm.showWarehouses) {
vm.headers.push({
text: vm.$ay.t("Part"),
text: vm.$ay.t("PartWarehouse"),
align: "start",
value: "displayWarehouse"
});
}
vm.headers.push({
text: vm.$ay.t("VendorPartNumber"),
text: vm.$ay.t("TaxCode"),
align: "start",
value: "displayTaxCode"
});
vm.headers.push({
text: vm.$ay.t("PurchaseOrderItemVendorPartNumber"),
align: "start",
value: "vendorPartNumber"
});
vm.headers.push({
text: vm.$ay.t("PurchaseOrderItemPartRequestedByID"),
align: "start",
value: "displayRequestUser"
});
vm.headers.push({
text: vm.$ay.t("PurchaseOrderItemWorkOrderNumber"),
align: "start",
value: "displayRequestWorkorder"
});
//--------------
}
@@ -943,6 +961,8 @@ async function fetchTranslatedText(vm) {
"PurchaseOrderReceiptText1",
"PurchaseOrderReceiptText2",
"PurchaseOrderItemList",
"PurchaseOrderItemVendorPartNumber",
"PurchaseOrderCustom1",
"PurchaseOrderCustom2",
"PurchaseOrderCustom3",