I'm using the IDP application and have been able to set it up and run with the provided test files. However, the configure tab only shows me the message saying I need to setup my credentials. I looked into it and it seems to be because of the integration "DU_listModels". When I run it I get the following error:
"Could not perform requested action, verify that the inputs are valid. io.grpc.StatusRuntimeException: INVALID_ARGUMENT: List of found errors: 1.Field: parent; Message: The provided location ID doesn't match the endpoint. For automl.googleapis.com, the valid location ID is `us-central1`. For eu-automl.googleapis.com, the valid location ID is `eu`."
I set my bucket to be east-4 so I used this in the connected system.
The Connected system seems fine as it authenticates properly. I tried changing the connected system region to "us-central1" and it authenticates but the integration throws following error.
"Could not perform requested action, verify that the inputs are valid. io.grpc.StatusRuntimeException: FAILED_PRECONDITION: The project doesn't exist."
I've been looking around but can't find any guidance. Appian does not provide any information on how to set this app. I've looked into the google documentation but can't figure it out. Does anyone have any ideas about it?
Discussion posts and replies are publicly visible
Could you ensure that 3 items: Your Google cloud project setup, your Connected System, and your admin console extraction smart service (if on Appian 20.2 or newer) are all set to "us-central1"? GCP itself only supports us-central1 and eu.
You can see this field in:https://docs.appian.com/suite/help/20.2/idp-1.1/installing-idp.html
Michael, I was able to figure it out. The issue was not the connected system nor g cloud setup. The package I downloaded from Appian had some configurations that were not mentioned on their site so I had to make some changes to get the right form to work.
Could you let me know what the unmentioned configurations were? I'd like to update the documentation to mention them.
Thanks!
The documentation I'm referring to is this: https://docs.appian.com/suite/help/20.2/idp-1/configuring-idp.html
The first screenshot shows a Document Channel grid which I did not see. I simply had the link that said to setup my credentials. The grid seems to list existing models, which I don't have on my google cloud account as I had just set it up, which in turn made the integration failed when pulling the models list and returned nothing. That was my diagnosis. The documentation goes into updating an existing configuration, but not creating a new one.
My solution was to setup the tab on the site to use the process model for setting up the configuration directly instead of the report in the meantime until I get my first configuration up and running.
I couldn't find any other information on Appian regarding this so for now this is my solution. If you have additional info, could you please share it?
Your app will not directly pull channels from your Google Cloud Project, you have to create the channels directly within IDP. The screenshot contains examples of what it looks like, but there should be a default channel.
It looks like the docs don't explicitly mention how to add a new channel during the configuring IDP page at this step of set up, so I agree that this could be valuable.
The grid does not appear until you've set up your credentials fully. Those are detailed in this step:
https://docs.appian.com/suite/help/20.2/idp-1/installing-idp.html#step-5-update-import-customization-file
which sets your connected systems through the import properties file. Once the import properties file is imported, the connected systems should have the necessary values to connect to GCP, as well as make the configuration page show the grid.
Michael, I only have the original Standard channel which came with the sql statements provided by Appian. I don't see any attachments. What screenshot are you referring to? This is what I have
Also, I have setup my connections by following that link. All connected systems authenticate and there are no errors there. The only issue is on the integration DU_listModels which returns the error as I mentioned earlier. Why would the system try to pull the models from google cloud if they don't yet exist?