New Fields in Projects
C
Carlos Diaz
Is there any functionality for the new fields added under Projects section (Customer, Project Status, Project Manager, Start/End Date, etc.). I think was really good to have them if can be used to do more advance filter on the desktop and mobile. But if is only to have that info under the projects name, then is completely worthless. I think might be good to have additional filtering options using these fields in additions to be create data events or even calculation fields inside the records using them. For example when set Project Status to complete then set all records assigned to that project as read-only or set a filter option by Client in the desktop version and mobile app.
J
Joe McCann
These are good ideas, the "projects" facilities should be extended to include more fields. We currently hand-code a json object pasted into the Description field in order to store arrays of variables like "client name", and the period of time for which that client owned the project like "client_from_date" and "client_end_date". Per we could just have a repeatable attached to each "project"? Some way to arbitrarily attach key-value pairs to them, that would be useful for sure.
Shawn Pickett
We have limited our use of Projects due to the limitations of what can be done with them and the lack of visible metadata. The existing columns could be useful if they were exposed somewhere. I agree with Jeremy Palmer's suggestion of exposing it through data events and allowing it to be customizable.
J
Jeremy Palmer
Please allow us to define our own metadata for projects. I have had to create a parallel app (really just a table) in Fulcrum to store all the other data I need to associate with each project. There are project codes used for client data delivery, bounding boxes to test whether record are in the right project, and an alias name for use in different contexts. Obviously, my specific needs would unlikely apply to anyone else, and vice versa.
I'd like the metadata to be accessible to data events with a function like PROJECTDATA(project_field_name) that returned null if the named field did not exist. I'd be content with a text editor to create JSON / JavaScript objects for each project, e.g. {client_id:"1MC09", originator:"AEC", doc_number:"1MC09-BBV_AEC-GI-GDD-N002-000001", geometry:"POLYGON ((419820 285232, 425331 290896, 415248 314505, 407282 317028, 407891 312348, 413199 288466, 419820 285232))"}. However, it would clearly be safer to have a little metadata editor where we give names and types to our metadata fields and then a form (similar to Fulcrum web app) and/or CSV importer to populate the data for each member.
PS: Perhaps an easy way to achieve this would be to allow us to link an app to the projects table. It would be automatically populated with one record for every project, with a matching _record_id for the project's _project_id. It would be editable via the Fulcrum web app, both to define the fields and edit records. (You could disable adding/deleting records, or make that equivalent to adding/deleting a project.) Or you could not enforce the links, so that the metadata would only count as linked if a special field existed (e.g. project_id) that matched a project's _project_id. That's effectively what I do now, but I'm unable to access the project metadata in data events, which I would really like to do.