-
Route.targetUrl gives me the workspaceObjectId during the new item workflow. But when I open an existing item, I get the itemId. For the workflow where the user wants to save a copy or go to a new empty item, seems like I need access to the workspaceObjectId. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Hi @dhrumil83, |
Beta Was this translation helpful? Give feedback.
-
thanks @ramizsha that works. 1 more related question: User opens a new item. Makes changes but wants to reset the view. When I call the same path via navigate, it does not call Can I force this navigate call, so it's like a browser refresh. Note: I can force the refresh by adding something extra(timestamp) to the path, but wondering if there is a recommended approach. |
Beta Was this translation helpful? Give feedback.
-
Hi, we don't have a specific recommendation for refreshing the page. However, I think using the navigation API for cleanup is probably not best practice, and I would implement a cleanup function instead that resets the view. |
Beta Was this translation helpful? Give feedback.
Hi @dhrumil83,
If you want to know for a specific item, in which workspace it is located, you can use the getItem API.
The result will contain the folderObjectId of the item which is the workspaceObjectId.