Tracks/types, filters, and locations are metadata for your content and cannot contain symbols that would act as a delimiter.
For example, the location field you import in your agenda and exhibitor locations is mapped on your floor plan graphics. If the location is called Reg/Bags, you would want to exchange the forward slash with a character that is not a delimiter. You could use a character called fullwidth slash instead: Reg／Bags
To ensure all filters and tracks are imported correctly and locations can be pinned correctly and display the animated pin drop, locations such as rooms, booths, and posters boards cannot include the following symbols:
- colon :
- semicolon ;
- backslash \
- double quotes "
- single quote '
- vertical line |
- equal symbol =
- hashtag #
You can include the following symbols
- hyphen -
- underscore _
- parenthesis ( ) or [ ] or { }
- star *
- plus +
- basic symbols @ $ % ^ & * < > . ! ?
Helpful replacements
You can replace delimiter characters with other UTF-8 characters that look very similar to the delimiter character, but are not an actual delimiter.
Replace the following:
- forward slash / with fullwidth slash ／ (Details) Note: standard forward slash can be used for locations
- semicolon ; with greek question mark ; (Details)
- apostrophe ' with acute accent ´ (Details)
- colon : with fullwidth colon ： (Details)
- pipe | with vertical four dots ⁞ (Details)
- comma , with single low quotation mark ‚ (Details)
FAQ
I have | in some filter keywords. When I click on a filter in one of the filter custom views (where the App Builder creates a custom view out of all my agenda filters), I get "No Results"?
The pipe character | is not supported within individual filter keywords.
For each filter (e.g. you may have a Topics filter for your sessions), the App Builder automatically generates a custom view listing all the filter keywords within that filter, so that you could link to it if necessary. In the custom filter view, the full keyword may still display correctly, such as D1|B3 Cardiology. But when you click it, the link that builds the session list treats | as a separator, not as part of the keyword.
That means the system may only use the first part, like D1, to run the filter. But there would be no sessions tagged with just D1, so the result will be No Results.