You’re offline. This is a read only version of the page.
I am looking into the possibllities of using af the field type: File.
I can't find much documentation from Microsoft on this and I am courious of the possibilites to use it in model driven app.
I have got a use case where we would like to add a file to record - both the record and the data is sensittive data, and only users with a specific security role should have access to the record and the file.
Therefore we can't use a standard attachment function on notes, and the customer prefers not intgrate to SharePoint.
So I am looking in to if this new field type file, could be a solution - and got some questions to clarify...
1. You can't add the file field to a model driven app form. But I found the tip from Joel Lindstrom, that you can add the field to a BPF https://crmtipoftheday.com/1366/make-file-type-field-required/
However when I tested it, I noticed that when you have added a file, it is not possible to change it - any solutions to this ?
2. Does the file field follow the normal security model ?
3. Where is the file data stored ?
4. If you delete the record, is the file then also deleted ?
5. I found very little documentation from Microsoft about this https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/types-of-fields#file-fields ?
- any other sources ?
For now I think SharePoint is the right solution for this task - but it would great to know if somebody else has used this new field type - and would be great to hear about your experiences :-)
By the way - there is also an interesting blog post about the topic here: https://debajmecrm.com/2019/12/16/new-data-type-filein-cds-all-you-may-need-to-know-about-it/
Hi Dorthe,
Model-Driven forms support is available as Preview since 2020 Wave 1, as per below:
docs.microsoft.com/.../large-file-image-support-model-driven-forms
Files stored through this attribute should be counted against CDS file storage, as per the new capacity model:
docs.microsoft.com/.../whats-new-storage
As file attribute are being treated as other attributes of an entity from the security perspective (and not stated differently on any public facing documentation I searched) I would expect it to follow the CDS / D365 security model.
Similarly, deleting the record would delete the bits that attribute has stored.
Share
Report
All responses (
142
