.fetchRelationships() showing outdated data

RE: .fetchRelationships() showing outdated data

AngelaIp — Wed, 29 Jan 2025 09:30:17 GMT

fetch is only used to get DB data.

Easy example: You have manually opened a Part in Innovator. Typically the BOM relationship is visible too after you have opened the item.

Now you can immediately use "get" to work with data from the BOM. Cause you already HAVE the data. It´s visible for you and present in the DOM. But if you need to work with data from the "AML" tab in a Method (without opening the tab), you need to "fetch" the data first.

"fetch" is just a command for the item dog. (Greetings to the attendees of Innovator Dev Course Gröbenzell 2018)

RE: .fetchRelationships() showing outdated data

Frank Guarino — Thu, 23 Jan 2025 21:19:29 GMT

Alright so .fetchRelationsihps wasn't showing outdated data. It was showing the db data (as we should know)

Why I assumed it was, was that the passed Item variable had outdated data within its node xml

To update the node's xml, please look at my larger comment which talks of using .getItemsByXPath

Thanks

RE: .fetchRelationships() showing outdated data

Frank Guarino — Wed, 22 Jan 2025 21:08:54 GMT

Oh I just didn't understand the C# method. All good, I don't think the C# method is using outdated data actually. Sorry for the previous comments Aras, I am quick to convict another

RE: .fetchRelationships() showing outdated data

Frank Guarino — Wed, 22 Jan 2025 20:59:17 GMT

In the C# method it calls .fetchRelationship() which seems to be outdated there. What I ended up doing was just letting my JS function finish and no longer call the C# function. Then I made a second button for the user to press after the processing was complete

If one tries to rebute by saying why not have JS promise method save the item and configure a onAfterUpdate server event, I'd be careful with that, as the onAfterUpdate would likely finish first and would also still be using old data, or atleast would need constant eyes on that method or atleast a headache to watch over an onsave of that, well that's me being lazy

RE: .fetchRelationships() showing outdated data

Frank Guarino — Wed, 22 Jan 2025 20:32:38 GMT

Ok so this does work - but. This works so the xmlDom is correct in the promise result.

I am iffy on this: When I take that promise result, I call a C# method afterwards, and that method is acting oddly as the output of that method is as if the xml is still outdated, despite me calling the C# method with item.apply()

RE: .fetchRelationships() showing outdated data

Frank Guarino — Wed, 22 Jan 2025 19:47:08 GMT

Did not work either actually. The server requests are updated, but the variable's dom still isn't...

RE: .fetchRelationships() showing outdated data

Frank Guarino — Wed, 22 Jan 2025 19:41:56 GMT

Nice I figured it out.

Inside the method, any manipulation done to the item in question should be carefully ensured that any manipulation is referenced in the xmlDom's own object (making a javascript copy of my variable which I will mention later still let the solution work (it did not inhibit it, it still worked))

The item in question was activity. The method manipulated its relationships via SQL (problem as above, with bug of not updating for promise function) and I instead fetched the relationships, called getRelationships, and then specifically did .getItemsByXPath to get the record I wanted to delete. Calling getItemsByXPath on the variable assigned with .getRelationships meant that I was in fact using a pointer to the already existing xmlDom.

From there, when the variable assigned with getItemsByXPath (<copying this one still works too), I was able to do .setAttribute("action", "delete"), .setAttribute("id", id) and then calling variable.apply(). This accomplished two things one: What the SQL already was doing (deleting), and 2: also updating the xmlDom of the Item activity for when I returned it it would reflect the operations done (the records were no longer there at all, hence the item with action=delete completed its performance and now was gone)

RE: .fetchRelationships() showing outdated data

Frank Guarino — Wed, 22 Jan 2025 18:58:16 GMT

Changing the requests in Method to AML did not work either