Murakami Akihiko @ Marubeni IT Solutions
My feedback
25 results found
-
20 votesMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
17 votesMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
39 votes
We have released this change for Copy, and the change for Move is coming in the upcoming months.
Murakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
6 votes
Thank you for your submission. However, this does not have enough demand in order to be prioritized.
We will reconsider with additional use cases.
An error occurred while saving the comment Murakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
69 votes
Due to higher priority initiatives, this has been deprioritized.
Murakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
10 votesMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
4 votes
We don’t currently plan to provide such an API, however please leave a comment if you have more information about how this would be used. In the interim, you can identify all of a user’s collaborations by requesting items in the user’s root folder (id = 0) and filtering out those where the owned_by user is the current user. This would require an additional API call for each item to get the collaboration id, but if you are only interested in knowing which items re collaborated versus owned by the user, it may be sufficient for your purposes.
An error occurred while saving the comment Murakami Akihiko @ Marubeni IT Solutions
commented
In current specification, the numbers of collaborated users are configured as CAN_VIEW_PATH = True via API and it is causing us big issue that we get the parents folders of actual invited folders included to the folder list of FolderID = 0.
-
411 votesMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
25 votes
Thank you for the suggestion. This is an interesting idea but not one we currently have on the roadmap. In the mean time, you can apply techniques such as caching (i.e. fetch what you need once for a session and keep it in local storage) to reduce round-trips, and the use the ?fields query string parameter to request only the minimal set of fields you need, which can reduce API response times.
Murakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
33 votes
This will be considered for the FY24 roadmap, not planned for FY23
Murakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
26 votesMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
291 votesMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
1 voteMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
1 voteMurakami Akihiko @ Marubeni IT Solutions
shared this idea
·
-
4 votesMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
1 vote
Thank you for the suggestion! At the moment there is no plan for this feature. We may look into this in the future.
-
2 votesMurakami Akihiko @ Marubeni IT Solutions
shared this idea
·
-
1 voteMurakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
24 votes
We'll be evaluating improvements to Shared Links later this year and will provide an update at that time.
Murakami Akihiko @ Marubeni IT Solutions
supported this idea
·
-
72 votes
Not planned for now. When we update admin login flow in FY20 H2, this will be under consideration.
Murakami Akihiko @ Marubeni IT Solutions
supported this idea
·
I also strongly do support this request.
When a malicious user tries to steal confidential information without being noticed by SIEM, he/she searches for some specific keyword to reach to the target document.
We need to detect those suspecious user who searches for those word.