Create and manage web files
A web file represents downloadable file in a portals website, used to store images, documents, and any other file type.
To store the actual contents of a given file, portals uses the attachment feature of the notes associated with a web file record. The file attachment of the newest note associated with the web file is used as the file content. As such, the size of web file content that can be supported by portals is determined by the note attachment size supported by your Dynamics 365 for Customer Engagement installation.
Manage web files in Dynamics 365 for Customer Engagement
Web files can be created, edited, and deleted within Dynamics 365 for Customer Engagement.
Sign in to Dynamics 365 for Customer Engagement.
Go to Portals > Web Files.
To create a new web file, select New.
To edit an existing web file, select the web file name.
Enter appropriate values in the fields.
Select Save & Close.
Manage web files on a portal
For portal users with content management permissions, files can be managed using the portal inline editing interface. If your user account has been assigned the necessary permissions, the inline editing interface will appear automatically when you sign in to the portal.
Create a web file
Sign in to the portal.
Navigate to the parent page under which you would like to add a web file.
On the portal inline editing toolbar, select New > Child file.
Enter appropriate values in the fields.
If you select a file to upload before providing a name or partial URL, those will be automatically populated base on the name of the selected file.
Edit a web file
Sign in to the portal.
Navigate to the parent page under which you would like to edit a web file.
On the portal inline editing toolbar, select Children.
In the child editor dialog that appears, you can delete and reorder any of the child entities of the current page.
To edit an individual file, select the edit link on its list item.
Update the values in the fields as required.
To update the actual contents of the existing file, upload a new file. This will replace the existing file content for the web file.
When a web file is deleted through the portal front-side editing interface, its record is not deleted permanently from Dynamics 365 for Customer Engagement. Instead, it is moved to the Inactive state. It will cease to be visible on the portal, but can be viewed or reactivated by a Dynamics 365 for Customer Engagement user.
Web file attributes
The table below explains many of the standard web file attributes used by portals. It is important to note that the way in which many of the content/display-oriented attributes are rendered is controlled by the page template used, and thus by the portal developer.
|Name||The descriptive name of the entity. This value will be used as the file title in most templates (e.g., for link titles). This field is required.|
|Website||The website to which the entity belongs. This field is required.|
|Parent Page||The parent Web Page of the entity, in the website content hierarchy.
While a file is not required to have a parent page – in some scenarios, for example, a file may have a parent blog post instead – providing a parent page is the recommended configuration in most cases.
|Partial URL||The URL path segment used to build the portal URL of this page.
The single root (Home) page of your website – the single page that has no associated Parent Page – must have a Partial URL value of /.
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-release.pdf, Site_Header.png.
|Publishing State||The current publishing workflow state of the file, which may dictate whether or not the file is visible on the site. The most common use of this feature is to provide published/draft control over content.
Users with content management permissions may be granted the ability to use Preview Mode, which allows these users to see (preview) unpublished content.
|Display Date||This attribute is a date/time value that can be used by a template, purely for display purposes. It has no functional implications, but can be useful for things like, for example, manually specifying a published date on a press release document.|
|Release Date||Controls a date/time after which the file will be visible on the portal. If the current date/time is prior to this date, this file will not be visible. (The exception to this is that users with content management permissions may be granted the ability to use Preview Mode, which allows these users to see (preview) unreleased content.) This is useful for controlling the release of time-sensitive content, like news or press releases.|
|Expiration Date||Controls a date/time prior to which the file will be visible on the portal. If the current date/time is after this date, this file will not be visible. (The exception to this is that users with content management permissions may be granted the ability to use Preview Mode, which allows these users to see (preview) expired content.)|
|Summary||A short description for the file, this value will generally be used to add a description of the file to portal navigational elements that render a link to the file.|
|Hidden from Sitemap||Controls whether or not the file is visible has part of the portal site map. If this value is checked, the file will still be available on the site at its URL, and can be linked to, but standard navigational elements (menus, etc.) will not include the page.|
|Display Order||An integer value indicating the order in which the file will be placed, relative to other entities with the same Parent Page. This controls the ordering of files and other site map entities when, for example, a list of links to the child entities of a given page are rendered on the portal.|
|Cloud Blob Address||A text value in the format
|Content-Disposition||Options are inline or attachment. If inline is specified, the browser should attempt to render it within the browser window and if it cannot, it will prompt the user to download or open the file. If attachment is specified, it will immediately prompt the user to download or open the file, and not try to load it in the browser, whether it can or not.|
|Enable Tracking||If enabled, every request for this web file will be logged. A Web File Log record will be created with the date & time, IP Address, and the contact record if the user is authenticated.|
Send feedback about: