Can someone explain what exactly is metadata, and what is the role of metadata in the datahub and how it is better to calculate the metadata in the datahub itself rather than importing it to other spoke models?
Hello @Vikas7895
Meta data is nothing but your required(dimentionality) lists information along with attribute data, and in datahub we will maintain/store these are flat lists. Data hub is the single source of truth (for multiple spoke models) and we will not do any calculations.
We will bring that meta data into spoke models either flat/hierarchal lists and attribute information in system modules which are referred for multiple calculations.
Hello @Vikas7895 ,
In simple words, Metadata is data that is required to create lists, Properties, subsets. In Data Hub, this data shall be calculated. For example, a file contains Transactional data which has SalesReps, Products details. From this you can create SalesReps list, Products list by finding Unique items. Later, import those unique entries to create/update lists in spoke models.
Does anyone have any documentation on the trade-offs of having 1 model for all components of planning (service revenue, product revenue, labour planning), vs multiple models 1 for each and a consolidation model to tie it all together?
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
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.…
