Is there any way to suppress messages after importing into a List that are a result of the 'Another row has already been processed with this key'
I don't think you can simply disable warnings, but could you please advise why you need to do this?
BTW, If this is a result of building a list from the same source as data load (for example data contain periods causing key to be duplicated), a separate upload based on different source selecting unique items could help.
The reason for this is because when end users run a process containing several list import routines, when the confirmation message shows the warnings then they have to open each one to check if there are any errors and 99% of the time it is for the 'Another row has already been processed with this key' type message rather than a 'real' import error as such.
It is a building a list from the same source as data load type of thing, so maybe a unique items selection would be the best option.
Yes that is correct, it is a model that I have inherited and has been in use for some time. Basically there is one import process that pulls in data from the data hub model, this process updates several modules and lists in one process and on the lists it is set to only import the first instance of the list item, therefore we end up with a warning message each time. Usually the end user would ignore those messages but when we have new starters, they think that something has gone wrong with the import so just trying to eliminate that.
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.
I have a question about the new Expand or collapse grid rows option. Is it possible to publish a grid containing a 5-level hierarchy so that all items from levels 1 and 2 are always visible? And I do not want to use a filter for this.
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…