Currently, I am trying to take one value from the home dataview and divide it by the total of another dataview on the screen but whenever I incorporate both dataviews my nexel column becomes blank (please see image)
You may need to approach the problem from a different angle. To carry out actions on the results of calculations with NEXEL, those results should be stored in a cube - committed. To carry out the work on the fly, you would have to also use a procedure to save (commit) that work.
I haven't time to go through the steps right now but here is a solution I proposed to another community member for an entirely different issue but in which I outline how to configure Nexel and procedures to work as you describe.
Also,Pietro Ferrari recently explained the reasoning for committing the results in another user issue. You may find his explanation helpful with understanding Nexel more thoroughly:
Please reply with any queries you may have and I will assist you in achieving what you need.
I have discovered CROSSVIEW.
Jack, Hi again.
I just picked up on a word in the title of your post and discovered that it is a very awesome feature of NEXEL. I am talking about 'Crossview'. so, thank you very much and sorry for responding without actually understanding your issue fully even though it was because I didn't know what 'Crossview' actually was.
...to your problem. I do not know the setup of your dataviews and cubes and so cannot respond with an actual fix. I can, however, provide you with a test model that functions in a way that may be useful to you.
Malav Shelat had an issue where he appeared to be 'losing' the NEXEL formulæ. I suggested that he might not be completing the configuration by refreshing the screen on the client model and posted the attached model to him to discover if it helped; I await his response. I then found myself reflecting on your own issue and my original response, sent before I had picked up on your actual issue with this fantastic new feature called 'Crossview'. So, having now dived into 'Crossview' I thought I'd return to your post and attach this update in the hope that it might help you determine the cause of your own issue.
In case you have not yet found it, the HELP guide also has some useful info on NEXEL which I have now read too.
Please let me know the outcome, whether assisted by my posts or not. I really would like to learn of any issues with NEXEL as I intend to use it quite extensively going forward.
Retrieving data ...