User are not able to see Custom Properties

[vikra...@gmail.com]

Hi,

I am trying out a setup for my team and this is what I did. In Drive, I created hierarchy of folders like this:

Documents
|_ Design
|_ Purchase

Then I opened Documents folder in Metadrive, and added bunch of custom properties to that folder.

After that I gave user1 access(read/write) to Design folder only and user2 access(read/write) to Purchase folder only.

But it looks like neither user1 or user2 can see the custom properties when they open Design or Purchase in MetaDrive.

I am able to see it when I open any of folders in MetaDrive.

Any thoughts on what I might have done wrong? Or please advice on the right way to setup where I can create custom properties on a parent folder which is accessible by users on the sub folders.

Regards,
Vikram

[support]

Hi Vikram,

To load the custom properties from a parent folder when openning a subfolder users need to have atleast read access to the folder where the custom properties are created. That's why you can see these properties with your account (with access to the parent folder) but the other users can't do it.

Also if you want to access from deeper levels, you need to have read access to all the subfolders above, because Metadrive navigates throught all the parents from a subfolder until it finds custom properties.

You can take a look on this video: https://www.youtube.com/watch?v=CvPU5NLov-U

Let us know if it's clear.

Best Regards

evenBytes Team

[vikra...@gmail.com]

Thanks. It make sense. I will rework my setup.

[vikra...@gmail.com]

After giving everyone the read access to the Documents folder, both user1 and user2 can see the custom properties in the folders they have access to.

But, now, they are not able to create document/sheets directly from MetaDrive which was previously working fine even though they have "Organize, add, & edit" access to their respective folders.

Thoughts?

[support]

Hi Vikram,

Users cannot create documents/sheets because they are inheriting their read permissions from the "Documents" folder, instead of using their permissions in "Design" or "Purchase" folders (Organize, add & edit). This was an unknown behaviour which have been escalated to the engineering team and it will be fixed soon.

As a workaround we suggest that you give edit access in the "Documents" folder, so that users can create files until the fix arrives.

Thank you for your feedback!

Best Regards

evenBytes Team

[vikra...@gmail.com]

Appreciate the quick response! Let me think about how I want to go implement this for my team till your engineering team fixes the permission issue.

[vikra...@gmail.com]

I gave Edit access to everyone in the "Documents" folder after which I can see the option to create documents directly from MetaDrive.

Now when I try to create a new Document from MetaDrive I see following error:

{
"error": {
"errors": [
{
"domain": "global",
"reason": "notFound",
"message": "File not found: 1V92_hZRo-c1juqJZhRZtmO0227GOjz7k-TFkNddC37U.",
"locationType": "parameter",
"location": "fileId"
}
],
"code": 404,
"message": "File not found: 1V92_hZRo-c1juqJZhRZtmO0227GOjz7k-TFkNddC37U."
}
}

What might be wrong?

FYI, the docs created directly in drive can be edited successfully (able to update custom properties without issues).

[support]

Hi Vikram,

We have been checking our system and it seems there have been some problems with the new/copy function from Google Drive API. We have been trying to replicate the issue too, but there was no problems for us.

Could you provide us more information about the problem?

• Is this happening everytime you try to create a document?
• Is this happening only to you or to every user?
• Which browser and version are you using?
• Do you know if the functionality was working before?

I believe this information could be enough to track the issue.

Waiting for your answer and thank you for the feedback!

[vikra...@gmail.com]

Here's the info you required:

Is this happening everytime you try to create a document?

yes, everything when I try to create a document. It is working fine for Edit

Is this happening only to you or to every user?

yes, happening to all users

Which browser and version are you using?

Google Chrome is up to date
Version 66.0.3359.181 (Official Build) (64-bit)

Do you know if the functionality was working before?

Yes. It used to work OK before

Thanks for all the support and answers. You guys are great.

Let me know if I can provide any additional info.

Test,
Vikram

On Monday, May 21, 2018 at 10:35:57 AM UTC-7, support wrote:
> Hi Vikram,
>
>
> We have been checking our system and it seems there have been some problems with the new/copy function from Google Drive API. We have been trying to replicate the issue too, but there was no problems for us.
>
>
> Could you provide us more information about the problem?

> Is this happening everytime you try to create a document?Is this happening only to you or to every user?Which browser and version are you using?Do you know if the functionality was working before?

[vikra...@gmail.com]

Any update on the issue? Can I provide more info?

[vikra...@gmail.com]

If it helps, I notice MetaDrive is calling "copy" method [https://www.googleapis.com/drive/v3/files/{fileId}/copy] instead of the "create" [https://www.googleapis.com/drive/v3/files] of the Google API when I am creating a new document.

[support]

Hi Vikram,

Sorry for the late reply and thank you for your feedback.

We have managed to replicate the issue and that was the problem. Metadrive is calling copy method in blank documents due to previous issues with create method and, apart of that, we believe you have some settings in your domain that avoid users to receive documents from external domains. Could you confirm this information so we can ensure that the problem is happening due to this setting?

This is the option we believe is triggering the bug:

You don't need to change these settings, we are working on the fix and it will be implemented as soon as possible.

Thanks again for your feedback and sorry for the inconveniences.

Best Regards

evenBytes Team

[vikra...@gmail.com]

Hi,

Confirming the setting is set to false like your screenshot.
Appreciate you looking into this.

Regards,
Vikram

On Wednesday, May 23, 2018 at 7:38:39 AM UTC-7, support wrote:
> Hi Vikram,
>
>
> Sorry for the late reply and thank you for your feedback.
>
>
> We have managed to replicate the issue and that was the problem. Metadrive is calling copy method in blank documents due to previous issues with create method and, apart of that, we believe you have some settings in your domain that avoid users to receive documents from external domains. Could you confirm this information so we can ensure that the problem is happening due to this setting?
>
>
> This is the option we believe is triggering the bug:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

[support]

Thanks for confirming, Vikram.

We are working on it and there will be a minor update during next week with fixes from the issues you have reported.

Best Regards

evenBytes Team

[Admin MetaDrive]

Hi Vikram,

We would like to inform you that we have already applied the fixes in Metadrive.

Let us know if both cases are working for you now:

• Problem with inherit permissions from parent folder
• Problem creating new documents directly from Metadrive

Best Regards

evenBytes Team

On 24 May 2018 at 18:45, support <ad...@metadriveapp.com> wrote:

Thanks for confirming, Vikram.

We are working on it and there will be an minor update during next week with fixes from the issues you have reported.

Best Regards

evenBytes Team

--
You received this message because you are subscribed to the Google Groups "support-metadrive" group.
To unsubscribe from this group and stop receiving emails from it, send an email to support-metadrive+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Vikram Modi]

Great! Will try it out ASAP.

Vikram

On Fri, Jun 8, 2018 at 1:54 AM Admin MetaDrive <ad...@metadriveapp.com> wrote:

Hi Vikram,

We would like to inform you that we have already applied the fixes in Metadrive.

Let us know if both cases are working for you now:

• Problem with inherit permissions from parent folder
• Problem creating new documents directly from Metadrive

Best Regards

evenBytes Team

On 24 May 2018 at 18:45, support <ad...@metadriveapp.com> wrote:

Thanks for confirming, Vikram.

We are working on it and there will be an minor update during next week with fixes from the issues you have reported.

Best Regards

evenBytes Team

--
You received this message because you are subscribed to the Google Groups "support-metadrive" group.

To unsubscribe from this group and stop receiving emails from it, send an email to support-metadr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "support-metadrive" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/support-metadrive/JkU2DGP9T20/unsubscribe.
To unsubscribe from this group and all its topics, send an email to support-metadr...@googlegroups.com.