I am trying to create an automation using Speckle Automate and basing it off of one of the functions that were published during the previous Automate phase. I followed the steps, including adding the token and URL of the server, and then committed the changes to GitHub. The changes are saved and I set a release for the function but I am still getting the error that the function needs at least one release to be used in an automation. Nothing I have tried changed that issue. What am I missing?
From a workspace > automations > create new function
Select either template
Follow link to the github repo
Making no code changes, create a release with tag â1stâ < can be anything
Action proceeds to deployment
There is no need to make any changes to tokens or server URLs. In case you were pointing the function and hoping to run on your own server, this will not work as Automate is exclusively available to app.speckle.systems from with Workspaces at this time.
It does not give me last published no matter how many times Iâve created a release, pushed it back to GitHub, or done anything else. I am editing the code on Visual Studio and pushing it back into GitHub before creating the release. It now showed that there has been an error in building the repository so maybe that is it. I will share the repository now to see if there is anything beyond just that error.
The Automation now works. The errors were a case of using foreach on an integer (which was fixed). Specifically, this was the error.
foreach statement cannot operate on variables of type âintâ because âintâ does not contain a public instance or extension definition for âGetEnumeratorâ
It was handled and fixed. My next issue turned out to be in the FunctionInputs struct where the class was not recognized, most likely due to an indent issue. This was also addressed and now the Automation is working.
I am running into an issue where the function is reading the parameters but is not reading the fire rating within the parameter variable.
The first part shows that the parameter is being read but it will not reach the second part where the Fire Rating is then read. Was there a change in the ID of the fire rating since this code was first written or is it something else?
I should note, in addition, the loop only seems to go to the third section of the data and doesnât enter the parameters tab. I note that from the ID that gets printed being only the second to last one.
That fire rating example may not have ever worked to completion. I donât recall there were a spread of fully functional and demonstration only of an idea for a specific dataset.
Weâve removed them for this reason.
We will be publishing soon public functions that are packaged as-is and also documenting example functions for adaptation. Handling revit parameters is certainly going to be part of what we demonstrate but the functions from closed beta, even if they worked a year ago have not been updated to all the SDK changes made since then.
I see. I wanted to make sure of this before continuing. Thank you for the support. We will be continuing using Automate on our end with the information we have been given.