Challenge #105: Think Like a CSE… Tools are missing!

[geoff_zath]

Found the original API key but it doesn't appear to work? Stuck with the demo key.

Spoiler

[SylwiaDragon]

I have inserted the macro to the canvas, and then exported workflow with all it's assets.

[tristank]

Pretty reasonable challenge. Put in a new macro and originally changed it to UNC path until I looked at solutions and realized that relative would make more sense based on the info we had. Changed it to relative and exported it as a packaged workflow. Had no idea how to tackle the bonus ask so it was cool to see the users messing with the XML to keep everything the same (something I'm not yet very familiar with but I should get try to get more comfortable doing)

Spoiler

[mithily]

Spoiler

EDITED THE MACRO PATH IN THE XML AND IT SHOWED ANOTHER WAY IS TO MOVE THE MACRO TO THE USER SETTINGS MACRO FOLDER AND THEN INSERT THE MACRO; DELETE THE OLD MACRO WITH THE ? AND WIRE UP THE MACRO AND YOU SEE THE PICTURE. i ALSO EXPORTED THE WORKFLOW THIS TIME SO THE MACRO IS PACKAGED WITH IT

[bo_peng2022]

My solution

[ed_hayter]

Spoiler

Interesting debugging case. Redragged in the macro from an alternative location rather than the macro repository.

Perhaps not the best way of doing things.

[gawa]

Done

Spoiler

[Tokimatsu]

Done

Spoiler

Open Reporting_Workflow.yxmd by notepad. Find "AstronomyPictureOfTheDay.yxmc". Edit the path.

 

[Hammad_Rashid]

[Rob-Silk]

Solution(s) outlined below:

Spoiler

Two methods that I can think of to achieve this

1. Most direct method seems to be to update the broken macro path in the main workflow XML - the workflow expects to find the macro in a "Macros" sub-folder relative to the main workflow path

Open the workflow file in a text editor (I prefer VSC for this sort of thing), find the offending line and update to point to the path where  the provided macro is saved, save the main workflow and re-open in Designer.

(Note - if you save the main workflow with a broken macro path reference, then the broken link will be lost from the XML file next time you try this trick and you get an empty <EngineSettings /> tag instead)



2. Alternatively, use the provided macro file to insert a new copy onto the main workflow canvas, then access the XML settings of the original (broken link) macro tool and replace the new tools settings with these using the XML editor




3. Having fixed the workflow with a working macro, make sure to set all dependents to use relative paths and then export the workflow with the "relative-path" macro as a .yxzp file so that the next person doesn't have the same issue.