Help required: Creating Generic Structure Tree view for SP12 environment (similar to VM-sample-app designed for SP14)

[sachinbijadi]

Is it possible to add a new relationship type with the 'generic item structure' view for the sample application in Innovator 11sp12 like the one provided in the application for SP14? I assume this is quite similar to the BOM structure view using the Multilevel BOM relationship used in the part item type. Would it be possible for someone to guide/ provide sample code, on how to set this up, as this is a really useful feature to see the whole configured superbom structure, instead of having to click through and open each level of the hierarchy

[sachinbijadi]

how can this be created in the app in SP12? Any help would be greatly greatly appreciated! Thanks!

[cgillis-aras]

It looks like that relationship tab uses a custom form to generate the tree of the Generic Item Structure, but you could achieve something very similar using the standard Query Builder and Tree Grid View functionality in 11.0 SP12.

[sachinbijadi]

Can the code behind that form (as written for the SP14 version) be shared here? Since I am not really a coder, that could be useful reference for me

[cgillis-aras]

You can find the Form in the TOC under Administration > Forms and searching for cs_sample_GenericItemFamilyTree. There is an HTML field as well as several Form Events that are responsible for building the view you see in the relationship tab. You could try using the methods and HTML as-is in your SP12 instance, though it hasn't been tested.

[sachinbijadi]

@cgillis-aras - that form does not exist in the SP12 version. Would it be possible, if you have access to the form in an SP14 instance, share the html code? (Also is there a video somewhere on the forum that shows what those form events are, etc.? Any guidance in that regard would be super useful)

[cgillis-aras]

Hi @sachinbijadi, I'm not sure if this form was available back in November, but you can now find it on the master branch of this repository here.

You can try merging that Form and it's dependencies into your SP12 import package. This project is an app built by our development team to show off the Configurator Service APIs, and my guess would be that this functionality is not version-dependent and was created as there was more development time for the later versions of this app.