If you are asking on App10, yes, this is possible to do .

If you are planning to use OpenAPI Power Apps doesn’t support V3 yet(as I remember). So have to use V2. You can find out some details on it on the following link (Technical Documentation → IFS Administration & Configuration Guide in IFS Aurena → Integration → API Documentation)

https://docs.ifs.com/techdocs/default.htm?openpage=https://docs.ifs.com/techdocs/Foundation1/040_administration/default.htm

Hi!

I’m looking into using power apps with IFS. I assume that I set up a custom Connection in Power Apps. There are two options for Open API, “Open API” file or “OpenAPI from URL”.

If I can use URL, what URL would that be?

For example I would like to add business opportunities to IFS CRM.  https://test.com:48080/main/ifsapplications/projection/v1/BusinessOpportunityCreation.svc/$openapi?V3

Is there some documentation, Step by step, how this is done? It would be really great to have an example for this.

Hi, I am in the process of creating a connector. I could successfully link to powerautomate and powerapps, altough I am still not able to create triggers in powerautomate. Anyone succeeded?

Hi All, 

For anyone still wondering about this, you do not need to create a connector. You can simply use the HTTP function to send your instructions to Alliance in line with the integration guide documentation. 

Setup a login HTTP request and retrieve the session ID result using convert to text function. Then use the captured session ID string in all of your subsequent instructions in line with the integration guide. 

I used postman to help me identify how to wrap the xml commands correctly. 

You can even loop through sharepoint lists etc so your end users can put a load sheet in a folder with a specific name and press run. 

Just don’t forget to send a log out HTTP command at the end of your flow. 

Hope that helps someone. 

Linked actions successfully. Triggers not. 

Sorry, that is not really the same IDKFA. For many reasons which are related to the very nature of custom connectors. 

Yes that is correct, it is not the same thing. But it is easy and it does work. So it’s a viable solution for OP.  If custom connectors work for you then no worries at all, I’m happy for you. 

Hi All. We are trying hardly now with the IFS Cloud. We are able to invoke the REST APIs via the postman according to the training material in the IFS Academy, but no luck with the Power Platform. Any recent experience or know how available? Thanks!

Hi @jaryskorys 

We have done that and please refer my blog post below which has a step-by-step guide on how to connect IFS Cloud with PowerApps platform.

https://dsj23.me/2023/08/08/getting-started-with-microsoft-power-apps-with-ifs-cloud/

At Align Consulting,  we are exploring the integration possibilities and expanding our expertise on MS power platform and IFS Cloud. Please get in touch if you need any help.

Cheers!

Damith

We will try. Thanks a lot!

@jaryskorys , Jarek, Did it work for u

Long time no see :)

Cheers

Pankaj

Long time no see indeed. The blog post is a real gem for us, but the original problem was our global network security, which we managed to fix eventually.

My team is going through the same thing right now.

@jaryskorys what was the global network security change that needed to be made?

I’m hoping this is our exact issue

@dsj I followed your instructions in your blog but must be missing something.

I have setup up my IAM client with the End User Authentication (Authorization Code Flow)

I have added my redirect URL from my custom connector back to the IAM client as the redirect URI and when trying to test the connector I get this error:

The request failed with client error: 'Input parameters are invalid. See details for more information. Details:OAuth2 Authorization Flow failed for service Generic Oauth 2. OAuth 2 sign in 'OAuth2LoginStrategyCore' failed to exchange code for access token. Client ID and secret sent in form body.. Response status code=InternalServerError. Response body: { "statusCode": 500, "message": "Internal server error", "activityId": "redacted_num1" } Client ID and secret sent in Basic authorization header.. Response status code=InternalServerError. Response body: { "statusCode": 500, "message": "Internal server error", "activityId": "redacted_num2" } '. The correlation Id is 'redacted_num3'

What are we missing?

We can get this to work in Postman, but this has proven more difficult

Hi @PhillBronson 

Have you able to cerate a new connection and authenticate with IFS successfully before testing the connector?

@dsj I have not been able to test this connection any other way as the redirect for the IAM client is specific to that connector. Also I am not sure how you would test a connection from power apps without a connector, so I may be misunderstanding your question sorry.

I think in your blog, the very next step after configuring the authentication and saving. You go immediately to the Test tab inside the custom connector

However I’ve been able to successfully connect oAuth connection with postman.

Hi @PhillBronson If I remember correctly, we had to allow the authentication in our F5 proxy for specific url. Note, we host the IFS Cloud on premise.

@jaryskorys thanks for that! We have it working for basic auth through gateway but still haven't figured out doing this with a service user using Oauth

I do plan to come back with my final result, @dsj resources have been very helpful

Hi @PhillBronson 

Service user authenticates with client credentials grant type. Unfortunately it’s not supported by the power platform yet.

https://learn.microsoft.com/en-us/connectors/custom-connectors/connection-parameters#oauth-20

As a workaround, you may create a proxy API to do the authentication and build the powerapps connector with no authentication or API key authentication.

Check below post on how to build a proxy api using Azure APIM

https://dsj23.me/2023/11/06/creating-an-api-proxy-for-ifs-cloud-using-azure-apim/

Hope it helps!

Damith

The request failed with client error: 'Input parameters are invalid. See details for more information. Details:OAuth2 Authorization Flow failed for service Generic Oauth 2. OAuth 2 sign in 'OAuth2LoginStrategyCore' failed to exchange code for access token. Client ID and secret sent in form body.. Response status code=InternalServerError. Response body: { "statusCode": 500, "message": "Internal server error", "activityId": "redacted_num1" } Client ID and secret sent in Basic authorization header.. Response status code=InternalServerError. Response body: { "statusCode": 500, "message": "Internal server error", "activityId": "redacted_num2" } '. The correlation Id is 'redacted_num3'

having the same problem over here :/

@jaryskorys was the problem related to the reverse proxy please?

Yes it was