etc: if i wanna set new tasks enity in the form views of project enity，it cannot work, which can work in another view s
Thank you for revising the description , which has become more accurate, but have you received this demand?Will improvements be made?
We have had this request previously, but have no immediate plans to work on form view improvements.
Would love to have this too! The new pop-up forms have this functionality, but the “real” forms (in the sidebar) do not. It’s weird because you need to create the real forms to be able to select them in the popup, so I’m assuming its similar tech.
The work around is that we added in the description of the dropdown, to create a new xxx please go to: www.company.fibery.io/formview. This means they need to leave the context, add a new item, and then refresh the form losing all previous input (because it does not live refresh every time you press the dropdown), then fill it again. The problem is that we have this for 3 fields… meaning that they might need to fill in the (pretty long) form 3 separate times. This is really horrible. Asking them to “Please press “c” instead of using this form view” is not something we want to do… But might need to resort to doing at this stage…
Form view was primarily intended to support use cases related to collecting data from ‘external’ people, and pressing C is supposed to be the easy option for ‘internal’ users.
What are the disadvantages for you of using c method?
This makes sense, but even internally having an easy to use form you can point people to makes it most accessible for non-tech savy users.
Ideally I can send an email with a form saying, any expenses? Please log them here.
Now I’d need to say, any expenses? Please press “c” on your keyboard, look for “Source Document” in the database, then click on the text that says “Default” and change it “Request payment” then fill the form. Oh you opened a document and it’s just typing c in the document? No you need to click off the page, and then pres- yeah there you go.
Less elegant. Can’t you just do a permissions check to see if they can create? You already do in the internal forms (when pressing “c”). I don’t understand why it can’t leverage the same tech. The public user has no access to create, and so it won’t let them create.
I obviously don’t know the details, but in this example, I might just point them to a view of the expenses database, filtered to ‘Claimant is Me’ with the relevant fields showing and just ask them to add a new record.
But that’s not to say that allowing to create related items from Form View is not a useful feature that we need to add (and in fact something we have in the backlog).
Yeah, I thought about doing it this way, but it felt less intuitive still than seeing a “Forms” folder and “Request Payment” in there.
While its possible, and might be indeed the way to go for now, its not the ideal. Glad this feature is planned!