There is an equals join relationship between the Assets and History tables via the ASSET ID MATCH FIELD in both tables which causes it to be a one-to-many relationship. The History table has a foreign key field ASSET ID MATCH FIELD. The latter two fields will get changed to the current logged in user name and current timestamp whenever a change is committed to the record. Additionally, it has an auto-enter on modify modification name field (Modified by User) and an auto-enter on modify modification timestamp field (Modified Timestamp). The field is set to be auto-enter on create serial with increment 1 – meaning each newly created record has it set to an integer one higher than the previously created record. The Assets table has a primary key field ASSET ID MATCH FIELD of type number. The solution consists of two tables, Assets and History. The last modification time and modification user of each asset is tracked. Assets can be checked-in, checked-out and a review of the condition of the asset applied – the latter all being recorded in a history. The solution allows tracking of assets within an organization of various types, with photos, serial number and including calculation of depreciation values. The (Sample) Assets solution is one provided with FileMaker 17 as an example of a complete, albeit relatively simple, solution. This is supported in Beta 3 so you can try it out today. However LCFM Native comes with the ability for your app to run offline and for that, you might need to make minor changes to your solution to make it work. If you don’t want to sync, you don’t need to do this, your app will work without changes. LCFM Native allows you to sync your data from your Android app back to your FileMaker database and vice versa. Syncing your FileMaker solution – Overview Video: Setting up the Sample Assets FileMaker solution for sync
0 Comments
|