Poly ItemType - mapping properties of poly sources

RE: Poly ItemType - mapping properties of poly sources

Calvin Hernandez — Tue, 03 Oct 2023 09:35:12 GMT

I know this is an old thread, but this might help someone else. Here's a server method I created recently to accomplish something similar.

For the poly item and all the poly sources, I created a property called "item_number", and then just copied the value of the property I wanted to use into the "item_number" property after a new item is created. You can do this for any number of properties you need to use for the poly item.

You can also get creative and do this retroactively on existing items, which I had to do as well.

You'll also notice I use fake properties to keep other server events from firing recursively.

// Method name: op_SetItemNumberProperty
// Created on:  10/2/23
// Created by:  CJ Hernandez
    // rev_0: Updates the "item_number" property for poly sources


Innovator inn = this.getInnovator();
Item itm = this;
string property_to_copy = this.getProperty("copy_me","");
if(property_to_copy != "") {
    itm.setAttribute("action","edit");
    string item_number = this.getProperty(property_to_copy,"");
    itm.setProperty("item_number",item_number);
    
    //Add fake property to keep other events from firing
    itm.setProperty("ignore_this","1");
    
    Item result = itm.apply();
    if(result.isError())
        return inn.newError(result.getErrorCode() + ": " + result.getErrorDetail());
    else
        return result;
}
else
    return inn.newError("Could not read property value to copy.");

I call it from an onAfterAdd server method like this:

Item itm = this;

itm.setAttribute("action","op_SetItemNumberProperty");
itm.setProperty("copy_me",[NAME OF PROPERTY TO COPY]);
itm.apply();

//Insert error checking here
return itm;

Hope this helps!

RE: Poly ItemType - mapping properties of poly sources

AngelaIp — Fri, 07 Oct 2022 10:03:47 GMT

Hi Jan,

I agree, somekind of mapping logic would be the best solution. Even if you merge two or more ItemTypes inside an onBefore/AfterGet Method, it´s still would require a lot of coding.

Do you use a custom onGet Method or the Aras Federation sample?

I remember I still have this open post in this forum:

community.aras.com/.../who-is-using-the-aras-sql-federation-itemtype-sample-v3-1-and-can-share-experience

I use both version (custom and Aras) in parallel and both have their pros and cons. The Aras Federation sample contains a mapping ItemType so it´s faster to implement and doesn´t require custom code. But query speed is higher with the custom variant.

RE: Poly ItemType - mapping properties of poly sources

Jan Cvek - Akrapovic — Thu, 06 Oct 2022 18:40:16 GMT

Hi Angela,

Thanks for quick answer. As you mentioned I was hoping on some secret way of achieve this :D

Anyway I have an itemtype with onGet method implemented which call SQL stored procedure (to accept parameters for filtration) and it works.

But... to cover all possible combination of filtration (like, not like, equal...) and all type of properties (string, date, list...) for every column takes a lot of work and nerves.

I'm looking for more elegant way... with more configuration and less coding...

Maybe Aras only need to implement some mapping logic between poly source properties (maybe also some conversion logic...) and poly itemtype would be way more useful.

RE: Poly ItemType - mapping properties of poly sources

AngelaIp — Thu, 06 Oct 2022 14:01:46 GMT

Edit: The SQL approach will of course eliminate the permission model if you don´t include it into the SQL query by yourself. So it´s not the most secure variant.

You mentioned an onAfterGet approach. It´s not unlikely that some approach with onGet/onBefore/onAfterGet can work. Hope anyone knows more :).

RE: Poly ItemType - mapping properties of poly sources

AngelaIp — Thu, 06 Oct 2022 13:39:22 GMT

Hi Jan,

I personally would rename them, cause I like standardized naming of properties. But I understand the argument that you don´t want to touch too many Methods.
I assume the way PolyItems are built is a core feature, so we probably cannot directly influence it.

Some more technical approaches (not tested!!!):

Poly-ItemTypes are not real physical ItemTypes/tables. They are just SQL Functions that do a UNION of the various tables.

Idea #1: Change the function in SQL directly.... Ok, I am not sure if it´s possible at all. And of course it´s a modification that is overwritten all the time when you edit the ItemType. And it´s not visible for the Aras update team so if you don´t overwrite it, they definitely will. It´s not the best idea to be honest.

Idea #2: Make a custom SQL view and link it to your target ItemType via "onGet" server Method.

These ideas shall not be seen as final answers. I am also interested in this question! One of design mistakes of the early days of innovator was the name/title inconsistency. Regular Items often use the "name" property, while everything related to CM use "title" as naming field. Building PolyItems with these kind of ItemTypes creates exactly the problem you described.

Out of interest I made a quick SQL test by myself, and indeed a custom SQL call for the Poly could be used to link non-identical property names:

SELECT TOP(10) item_number, name from innovator.Part
UNION
SELECT TOP(10) item_number, title from innovator.EXPRESS_ECO

But as mentioned before, there are maybe better solutions out there. Maybe the "Morphae" ItemType contains some secrets that we haven´t discovered yet, not sure. There is also this TechTip which maybe helps: https://community.aras.com/b/english/posts/tech-tip-sync-a-poly-itemtype-s-properties-with-its-poly-sources

Angela