Feature(s) impacted
Observed behavior
The url’s are built differently based on views and teams
In certain cases the url mentions the entity’s name at the end like so …data/ENTITY_NAME/index
and others seem to have an id instead.
Can you explain this ? and is there a way to set it up differently ?
Example :
https://app.forestadmin.com/Libeo-admin/Production/Ops/data/**payoutRefund** /index
https://app.forestadmin.com/Libeo-admin/Production/Ops/data/**05132d90-a967-11ea-99e7-17f2b7a6bc57**/index
Expected behavior
All urls have the same structure
https://app.forestadmin.com/Libeo-admin/Production/TEAM_NAME/data/**ENTITY_NAME** /index
Context
- Project name: Libeo
- Team name: All teams
- Environment name: All environments
- Agent type & version: “forest-express-sequelize”: “^8.0.0”,
Hello,
To understand more your needs, why do you want to have the same structure for all the URLs ? What do you want to do ?
We’d like to be able to redirect users from Salesforce to specific views and team layouts
But don’t understand how to compute the urls
I envision that your team has access to the team and collection data from the CRM.
Regrettably, as the URL for the workspace and dashboard includes a UUID in its path, it is not possible to generate the URL from an external source. The UUID never changes, maybe you can keep a version of each UUID on your saleforce part.
But why is there a uuid on certain views for one team and not other teams ?
and same question for why certain views and not others ?
Some URLs have been converted to a user-friendly format, while others have not yet been updated. The process of updating all URLs to a user-friendly format is not yet complete.
I will push your needs to the product team to integrate it on the roadmap 
But you can confirm that these id’s won’t change by the time you make them more user-friendly ?
Yes, the IDs won’t change.
I will push your feedbacks to the product board to make the URLs more user-friendly. If the subject will be prioritized, we will notify you.