Hi Anaplanners,
Can you please guide me which Text Encoding should be used while import, when the data set have some data in Chinese Language.
Thank you!!
The encoding should be driven by your source. If you use something like notepad ++, open your source file and then click 'save as' you should see the current file encoding format.
That said I think UTF-16 is a common format for complex characters and I think GB18030 is a common standard in China, so I would try these and see if they work for you.
UTF-8 is least subject to variation and used by text/CSV exports. UTF-16 is supported but there are byte ordering (little-endian vs big-endian) variants and/or optional prepended byte order marks (BOMs) to consider. Both can represent the full set of Unicode code points supported by Anaplan.
Has anyone tested Analyst’s response quality/speed on large, sparse models (think 10+ dimensions, millions of line items)? Wondering if there’s a practical ceiling before it starts timing out.
We've been building a tool called aplan4sheets and we'd genuinely like input from this community — both on what we've built so far and on what we should prioritize next. The problem we set out to solve: Anaplan's Excel add-in is Windows-centric, and there's no real native way to pivot Anaplan data in Google Sheets. We…
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…
