Hana Workspace for attributeview

[former_member205400]

Hey dudes,

Our team is coming together and we wanted to start using the workspace for our views we are creating - attribute, calculation, etc.

So i did the following:

1) created a workspace,

2) enabled the Hana Development view

3) checked out a package (i was surprised here that i had to check out a whole package and not just ONE attributeview)

4) I went to the workspace to work on my object and find that the icon is thinking that it is a text file.

I'm surprised that Hana doesn t know what it is. I r-clicked on it and selected OTHER programs and it displays a long list of internal programs for editing.

I'm still not finding a program listing to edit the attriobute view.

Am I missing it somehwere in the list?

Also is it possible for me to only check out the ONE attributeview and not the whole package?

Mike

[thomas_jung · Accepted solution]

First check out must always be done at the package level.  Single file check out and editing is not yet supported nor planned for the near future. 

Modeler objects (Attribute View, Analytic View, Calculation View, Analytic Privileges, and Decision Tables) do not yet have their editors converted to run in the Project Explorer tool.  You can check out these objects but you will only see the raw, underlying XML.  We do NOT recommend that you edit these objects in this format.  You should only use the dedicated view modeler tools.  These tools currently only run via the Modeler/Navigator as they were not originally designed to edit local files but instead have an RPC connection to the HANA Backend.  Eventually these editors will be rewritten to work with the Team Provider/Projects/Workspaces; but this will not happen before SPS7. So for the time being you must work in two separate workflows - the legacy one for the items listed above and the new workspace/project based approach for all other development artifacts.

[former_member205400 · Accepted solution]

Thomas good response.

Couple Follow-Ups

1) I can't imagine checking out a package that has over 20 items in it. I haven't tested this but it seems to me that if I checked out a package with 20 items then my co-developers would not be able to edit them. Is that correct?

2) We are looking at how we jointly modify our attribute views and other modeling objects. I'm suggesting that the modeler work in his/her own package area and then "refactor" that object to a package location that gets final testing before moving getting tranported up the landscape. Is this your recommendation or do you have another methodology?

Mike

[thomas_jung · Accepted solution]

>f I checked out a package with 20 items then my co-developers would not be able to edit them. Is that correct?

Not at all.  The check out process doesn't lock the objects.  It simply copies to your local machine so that they are available for editing.  Multiple developers can certainly have the same packages checked out at the same time.

>Is this your recommendation or do you have another methodology?

I've never heard of anyone using that approach. Generally people simply edit the objects within their package hierarchy.  I'm not sure I understand the need to have objects move packages during the development process as you describe.