404 error on Get Space

[radhakrishna2331]

Hello,

We are trying to use Qlik Cloud Services within Qlik Application Automation. Some blocks work correctly and pass the domain in the URL as expected, but others do not. For example, we receive the following error when using the Get Space block. We are not sure if we are missing a configuration or setting. Appreciate any help. Thanks.

[marksouzacosta]

Hi @radhakrishna2331,

My first guess is that your user doesn't have access to the Space.
From Qlik Cloud Hub, try to reach the Space and check your security. Also, show the settings you are using in the Get Space block - you don't need to hide the ID, it is unique to your Tenant, no one can use it.

Regards,

Mark Costa

[radhakrishna2331]

Hi @marksouzacosta ,

Thank you for your response. I created the space where this automation resides, so I am the owner of the space, and I also hold Tenant Admin privileges.

Additionally, I noticed that the space shown in the screenshot below does not match any of the spaces currently available in our tenant. Could you please advise on how we can further investigate and debug this issue?

Thank you for your support.

[marksouzacosta]

Hi @radhakrishna2331 ,

Not sure if you already tried this but:

1. Select the Get Space block and click on the Space Id dropdown. Next, click on the do lookup search icon:

2. Select the Space Id you are looking for and that should be it:

Regards,

Mark Costa

[Shai_E]

Hi @radhakrishna2331 

"Additionally, I noticed that the space shown in the screenshot below does not match any of the spaces currently available in our tenant."

What does this mean? so if i understand you correctly the space doesnt exist based on the sentence above.

Thanks

[radhakrishna2331]

Thats correct. The space id that is showing in my screenshot error message doesnt exist when I go into administrator tab and also when I use list space block in qlik automation.

[radhakrishna2331]

Thanks, Mark. I’m working on an automation that triggers via webhook to push a version to GitHub when an app is published in any space. Hard-coding the space ID would break the automation for future spaces, so I need a dynamic lookup instead.

[marksouzacosta]

Oh, ok.

In that case, you can get both the Shared Space Id - the source Space - and the Managed Space Id - the target Space.

1. Start Block with the App Publish webhook

2. The Get Space for the Managed Space / Target Space

3. The Get Space for the Shared Space / Source Space

Please note that to test the Automation you must publish an application.

Regards,

Mark Costa

[radhakrishna2331]

@marksouzacosta , I don’t see separate Get Space options for Managed or Shared spaces in my Qlik Cloud Services. I only see a generic Get Space block. Am I missing something here? Also, the screenshot I initially attached to this post shows the error I received from Automation that runs automatically after publishing an app.

[marksouzacosta · Accepted solution]

The Get Space is generic and works for any type of Space in Qlik Cloud, and this is the one I'm using.

The thing is, in Qlik Automation, you are communicating these blocks, and you can reuse these blocks information across the whole Automation.

So, the very first block in my Automation, the Start Block setup to Webhook and to listen to the App Published event, will trigger as soon as any application in your Qlik Cloud Tenant gets published from a Shared Space to a Managed Space.

This Start block returns all the information regarding the published app as a JSON Object, including application information such Shared Space Id and the Managed Space Id. So, when using the Get Space block, you can pass to these blocks the Shared and/or the Managed Space IDs.

I did a small video to demonstrate how you can get these values in the Get Space block. I hope it helps!
Video link: https://youtu.be/7SuCvFdaEv0

And just in case you need, following the JSON codes to assign the Managed and Shared Space:

Managed Space ID

{ $.AppPublished.spaceid }

Shared Space ID

{ $.AppPublished.data.attributes.originSpaceId }

Regards,

Mark Costa