Allow linked entries to have a value
After selecting a database, one field can be selected as the value of the linked entry, allowing calculations and a column in Google Docs.
In example, if you had a database of parts with fields "id", "name", and "price", you could link to an entry in parts and use the price as the value. Then you can use the price in a calculated field and there would be a column in the Google Doc with the price as well.
This feature available in 4.4 beta version: https://groups.google.com/forum/#!topic/mementodatabase/hqVTUdlIAbA
-
mukura commented
(#{linkedItem1.price} * #{quantity})*#{customer.pricelevel}
Also there would be the need to be able to use a calculation such as the above as an argument in a logic calculation
if('#{item}','#{part}','#{labour}')
Returning 1, or 0
and within the same calculation field being able to further script both logic and math so if(
(if('#{item}','#{part}','#{labour}'),'1','(#{linkedItem1.price} * #{quantity})*#{customer.pricelevel})')Being able to throw in THEN, AND, OR would be huge - perhaps a new feature suggestion in itself
Id be quite happy to be able to purchase votes, or upgrade from commercial licence to ultra premium platinum club to get features like this
-
mukura commented
Rows and Columns
The Row is the record entry
The Columns are the fieldsThere are database apps that do this and once it is implemented here it will be fantastic
One issue I can see with it is with regard to calculations - say the parent library called "Order" links to the child called "Parts", and the library/entry select as it currently stands allows one to link multiple parts - when it comes to the price column feeding into the order we would need to be able to aggregate into a calculation/result for subtotals, which then in turn would allow for calculating sales taxes and grand totals - bearing this in mind it would also be great to apply calculations to each linked entry individually so for example if the order consisted of "Parts" and "Labour" the labour items could be discounted or multiplied depending on factors such as customer loyalty or overtime. From here it opens up the can of worms that then, given this type of usage scenario it would require dependant calculations, which possibly would need to cross reference a library called "Price Levels", which ultimately could be a field (column) in the "Client" Library which is linked to another library containing price level calculations AND has the possibility to be overridden or adjusted within the order.
This would be comprehensive.. I think
-
Harsha Munnaluri commented
This is a must need.
At least provide an option to use field from linked item to be used in expression.
Example expression - #{linkedItem1.price} * #{quantity}
here price is actually a field from linked item and quantity is a field from current item
-
Garrett Royce commented
A very easy, but limited way, to do this would to make an extra field function "value" and any database that links will use the value, much like the name field function is used whenever the entry is linked. The downside is all linking databases can only see one value and using the price in one linking database and the name in another is impossible.
-
Garrett Royce commented
Sorry, it should be "field" and not "row" in my comment. Each linked entry field can optionally have a field in the database that is linking and the doc would have a column with the value of the linked field.
-
Garrett Royce commented
A further development could allow one linked entry to span many fields by allowing the user to give each field in the linked entry a row. So, in the same example, the Google Doc could have 1 to 3 rows with the id, price, and name of the linked part instead of linking the same entry 3 times; once for each field.