Would anyone happen to know how I would be able to update some fields for future employees after already adding them to the template?
For example, I would like to update the department of this future hire I had forecasted. However, it's not an input cell and was pre-determined when I added a new employee through the "Insert Row" feature in the Vena ribbon. Is there a way I can change the department (Sales Team (Sales Team)) without having to delete the entire row by deactivating flags and re-adding back to the template? If someone only had contributor access, they wouldn't be able to do this or edit once after adding a future employee.
In the workforce template, if you add an employee to a department and added details, like Job Title, Start date and all the details and save data, these details are all saved in the database. So if you refresh the template you have all the details in your new employee and in the department you saved. If you thereafter realize that you saved this the wrong department and you don't need this future employee in that department, simply clear out any details you saved, such as hire date, salary (anything in blue), save data and refresh. Now there is nothing in the intersection and you can add this new employee by selecting a different department and putting that employee in the right department. This can all be done as a contributor. Give it a try and let me know.
I know this is a bit late but I change the intersection. I do not think this is common to do it this way though. :)
Thanks for weighing in, @Jessica Parker. Can you share a little bit about your process?
To dig a bit deeper on both options provided by Mark and Jessica above (thanks!):
The employee details get saved to the cube based on the details you entered. Once in the cube, the easiest way to update the relevant details would be to clear the details on the employee and save again (as mentioned by Mark). This would push the relevant details back to the cube.
If you feel comfortable with the Modeler/ETL interface, you could directly edit the cube through a "File to Cube" ETL Job that would edit the relevant intersection directly; which is the method mentioned by Jessica. This is a bit more straightforward, data backend wise, but it is a more advanced method.
My recommendation would be to go with the first method and let us know how it went.
Forum brought to you by Vena Solutions Inc.