I want to import duplicate detail-data into Module.....
When I imported, same departmentcode data which is second same data was rejected.....
dimension(departmentcode) is Fixed and unchangeable, How can I do this?
What dimensions do you have in the Target module? Only Department? is a numbered list?
Normally, it is possible to create a numbered list with the unique combinations of Department and Department Type (Fixed or unchangeable) where Department and Department Type are properties in that list.
Hope it helps
Alex
mcdvoice wrote: I want to import duplicate detail-data into Module.....When I imported, same departmentcode data which is second same data was rejected.....dimension(departmentcode) is Fixed and unchangeable, How can I do this?
The difference between import module and from module import foo is mainly subjective. Pick the one you like best and be consistent in your use of it. Here are some points to help you decide.
import module
Pros:Less maintenance of your import statements. Don't need to add any additional imports to start using another item from the moduleCons:Typing module.foo in your code can be tedious and redundant (tedium can be minimized by using import module as mo then typing mo.foo)from module import foo
Pros:Less typing to use fooMore control over which items of a module can be accessedCons:To use a new item from the module you have to update your import statementYou lose context about foo. For example, it's less clear what ceil() does compared to math.ceil()Either method is acceptable, but don't use from module import *.
For any reasonable large set of code, if you import * you will likely be cementing it into the module, unable to be removed. This is because it is difficult to determine what items used in the code are coming from 'module', making it easy to get to the point where you think you don't use the import any more but it's extremely difficult to be sure.
We have an Integration Process in Anaplan CloudWorks created by User X - No WSA (originally Full Access with top-level Selective Access, now changed to Planner Read Only with Selective Access unchanged) and scheduled by User Y - with WSA , who also created the Integration Flow. Internal (Full Access) is enabled within the…
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.…