A Website is the core entity of an Adxstudio Portals application. A portal application selects a single Website record, and this determines what portal entities – Web Pages, Web Files, Web Roles, Content Snippets, etc. – are applicable to this application.
With a Website providing an application scope, multiple distinct portal applications can be connected to a single CRM organization.
Determination of which Website record a given portal application is bound to is usually by the website's Name, specified in the configuration of the portal deployment.
However, it is also possible to control this by URL path prefix (see the descriptions of Parent Website and Parial URL under Attributes & Relationships, below), or by domain, using Website Bindings.
Managing Websites in CRM
For CRM users, provided the Adxstudio Portals customizations have been imported into your Dynamics CRM organization, Website records can be managed under the Portals tab.
Some secondary portal entities, such as Publishing States, may not be made available by default in the main CRM sitemap/sidebar. To manage these entities, launch the editor for the desired Website, and locate the desired entity in the Related entities sidebar.
Warning! When deleting a Website record, the portal entities related to the Website (Web Pages, Web Files, Events, Forums, etc.) will also be deleted. This is generally the desired behaviour, as it means an entire website and all its related data can be removed from a CRM organization in a single operation.
Attributes & Relationships
The table below explains the standard Website attributes used by Adxstudio Portals. Website has relatively few attributes – its primary purpose is in its many relationships to other portal entities.
The descriptive name of the website. This field is required.
The parent website of the website. This field can generally be ignored, except in certain advanced portal configurations in which a single portal application is bound to one "master" website at the application root path, with one or more "child" websites available at specific sub-paths.
The root URL path segment for all URLs generated for portal entities related to this website.
For example, if a portal application is deployed to be available at the root of the domain example.com, and this attribute has no value, a request to http://example.com/ will render the Home Web Page of the application Website (as the Home Web Page is required to have its Partial URL set to "/").
If this attribute is set to the value "my-website", the Home Web Page will instead have a URL of http://example.com/my-website/, and all pages in the website will have the same "/my-website/" path prefix.
In most portal configurations, this field can be ignored and left blank.
Partial URL values are used as URL path segments. As such, they should not contain illegal URL path characters, such as "?", "#", "!", "%". Since Adxstudio Portals URLs are generated by joining together Partial URL values with slashes ("/"), they should also not generally contain slashes.
Recommended practice would be to restrict Partial URL values to letters, numbers, and hyphens or underscores. For example: "press-releases", "Users_Guide", "product1".