This description is not clear and there is two problem. 1. This description only show examples , we can not judge wether our environment violate this limitaion. 2. This limiation is about only source column name? also target column name?
> Functionality: How would you like it to work in the future?
Please fix description to clear above two point.
Fortunately , at some my customer this limitation was suspect as the cause of crash and I was answered from support team these questions.
Specifically. Each answers are 1. #, \, /, -,? , *, [ , ] 2. Both source and target column names.
> Motivation: Why is the change important for your business? > Importance: What is the impact if the feature request is not approved? > Benefits: What is the impact if the feature request is implemented?
In general , custsomer design task by self checking limitation from user guide. But now because user guide is unclear , some customer ask us to check exact limitation , other customer creates high priority case after some business impact issue occur. These cause customer unsatisfaction and will result below. - Affect to subscription renewal or new sell. - Our (and your) support resource exhaust.
For example in above cusotomer's case , customer creates high priority case after some business impact issue occur. Qlik support suspected special characters are crash cause and we spent about one month to check the suspection. But as a result this is not the cause. If customer avoided using these special character by self checking , we needed not spent such wasted resource.
NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.
