![]() I was very hopeful that someone finally put together a database that would just work, but while there are some advanced features for power users some very basic things are missing, making this thing absolutely useless. Download the iPhone, iPad, and Mac apps for free. To sync data on multiple devices, install Ninox on your iPhone, iPad, or Mac. More than “just” a database, it’s an entire application development platform." Easily the best of the App Store databases." "I found it easy to create databases and tables, to import and export data, design appropriate layouts, powerful filtering for fields, and also a very good formula field. Ninox provides a large number of use cases, such as inventory, invoicing, accounting, CRM, event management, and real estate. The Ninox platform is used by individuals, start-ups, agencies, small businesses, and enterprises in a wide range of industries. Digitize your organization, improve your workflows, and become more productive. Suppose we have 1,000 new records uploaded by CSV, it would be logistically impossible to religiously click the button for each of the 1,000 new records.Ninox is an easy-to-use database app for your iPhone, iPad, and Mac to help you and your team create, connect, and collaborate with databases.īuild tailor-made business apps and databases, also for CRM and ERP, without a single line of code. Let y := last((select 'Raw PI ID' where 'LINKER 2' = x).Id) Again, this button is on the shipments table: I then created a button trigger (on the shipments table) that when pressed will link the item from the matching records from the shipments table to the PI ID table when clicked. I named this "SKU-PI ID" pairing column into "LINK" (from the Shipments table) and "LINK 2" (from the PI ID table). Next, since I don't want to deal with "and" qualifiers, and since the SKU-PI ID is unique, I can just concatenate both columns into a single array, thereby producing a unique SKU-PI column, reducing the parameter to match into 1 instead of 2. ![]() Firstly, since the "PI" on the shipment table can be added with other characters (PI USA, PI CA, etc), it can just be remedied by slicing the PI data into different arrays through their spaces, and then extracting the first word on the array, which would be the root PI ID. Essentially, it's a 1:N, Raw PI ID : Raw Shipment ID table relationship. ![]() These PI orders can be split into multiple shipment IDs. PI 1 from the table 'Raw PI ID' can be split into USA and Canada shipments, which when translated on the 'Shipment ID' table becomes, PI 1 USA and PI 1 CA). Now, for the 'Raw PI ID' table, we have a "PI" and the product ID represented by the column "SKU".įor the Shipment ID table, each shipment line item still has a "PI" column (but since the PI can be split into multiple shipments, the PI can change in nomenclature, ie. ![]() We can't restructure or combine these two tables as different teams (which work independently) work on each table, so restructuring them would burn more time than we can save. We work with both our distributor side and supplier side, that's why we have 2 tables PI- being the orders on our supplier side, and Shipments on our distributor side. So, we have 2 tables - Raw Shipment ID and Raw PI ID. Hi I'm sorry, I was making this post in a hurry. ![]()
0 Comments
Leave a Reply. |