Hi,When executing requests to API end points, whats the format of e-tags that is allowed.ive used an api imported to power apps where a sucessful patch request’s etag was like belowW/”{keynumber}”but with a http request in power apps, the request ends up likeW/\”{keynumber}\” the 2 \ characters are preventing the request from being completed, is the API’s back end setup to handle these characters?because leaving them in times the request out with a ‘internal server error’ and no real information on how to resolve the issue Kind regards, Brian
Hi, Would like to ask if there has been any efforts to produce an IFS connector for Power Apps, more specifically for a login process to the system? I am currently trying to design an app for an IFS cloud environment and have ran into a few walls along the way. The app manages deliveries and uploads signatures to each customer order (access to these api’s are completed and program works as intended) But my app lacks a LOGIN page to prevent access to the already authorized and connected oAuth2.0 based connections which are used by the API requests. From what I understand so far;Browser accessing IFS Cloud Aurena:-GET request returns the login page’s html and javascript’sUser enters creds and clicks ‘login’POST request is sent containing RAW username and password in the body(see below for post request extracted from fiddler4 - editted for data protection)--------------And finally a 302 response is received from IFS Cloud suggesting the credentials were correct. Could someone point me i
Hi, I am currently working on a project to simulate a signature handling process relating to customer order deliveries. The customer signs for a delivery which marks the order on the IFS Cloud 21r1 platform as delivered but I cannot use the MediaLibraryAttachmentHandling.svc and its end point [PATCH] /MediaItemSet(ItemId={x}) According to Fiddlers traffic logs ( and when a file is inserted via aurena’s UI ).There is an extension of this endpoint ‘/MediaItemSet(ItemId={x})/MediaObject HTTP/1.1’ with RAW data being passed as binary format of a .png image. There is no JSON body being attached as per the IFS API documentation. I am stuck at a point where I cannot understand how I can pass binary data in POSTMAN to this same endpoint. The API documentation isn’t providing any example other helpful instructions as to where the binary gets inserted so it can be passed to IFS’s database. When I copy the application/octet-stream used from the fiddler data, IFS returns a not supported error mess
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
