Couple of questions back to you:
- Where are you changing the URL?
- Can you give some examples of what you do in PE vs. what you're doing in MVC and what your outcomes are for both?
Also to clarify:
- Portal Engine used the
NodeAliasPath field to generate public-facing URLs
- MVC/.NET Core DOES NOT use the
NodeAliasPath field to generate public-facing URL slugs. The
NodeAliasPath field is mainly for doing look-ups for content in your content tree now. To get the public-facing URL you need to go to General > URLs and get the slug from there.
So while PE may be doing what you want it to and MVC is not, it may be a misunderstanding of the underlying changes and how routing works with Kentico Xperience 13.