latest posts

I was only able to send one parameter as multipart/form-data—two or more cause a failure, but I need to send more.

Works:

In JSON part header:
Content-Type: multipart/form-data
Content-Disposition: form-data; name="Action"

In JSON part:
ActionName

Doesn't:

In JSON part header:
Content-Type: multipart/form-data
Content-Disposition: form-data; name="Action"
Content-Disposition: form-data; name="Subject"

In JSON part:
ActionName
SubjectName

Unfortunately, I cannot install any MITM tools. I think an SDK is the only way :(

Marcin,
Szybki update - w najnowszej wersji 2024, ktora mozna juz pobrac (2024.1.1.248), ten blad zostal naprawiony.

Pozdrawiam
Dawid

Thanks for this useful information.

Hi Franek,

I wasn’t able to use the multipart mode
https://daniels-notes.de/posts/2024/importing-applications-using-an-application#request-body-type-multipart

But it could be different in your case..

I would suggest to add a proxy like HttpToolkit to view the raw outgoing request. You may be able to modify it in a way that the result would be the same as in Postman.
https://daniels-notes.de/posts/2022/debug-web-service-datasource

Best regards,
Daniel

Hi, I need to send data as "multipart/form-data" I am trying to configure the Request Body tab of the "Invoke REST Web Service" action.
I set the Body Type as "multipart" and the JSON part header as "Content-Type: multipart/form-data"

How should the value for the JSON part field be formatted? Should it be in JSON? (I have tried but without success.)

Dear All,
Thank you for your feedback regarding the Searching Structures functionality.
After careful, further consideration and direct discussions with many community members, we've decided to proceed with removing the Searching Structures functionality. While this may initially require an adjustment to your way of working, I'm confident that using reports with their comprehensive configuration options will provide a better experience in the long run. Just as a reminder - each newly created application automatically generates as well a default report.
While the Searching Structures control has served its purpose, it's now outdated and I believe it's the right time to just let it go.

Thank you again for all the comments, having such an active and engaged community is extremely valuable for me and our entire team. Please continue sharing your thoughts and suggestions in the Forum to help us improve WEBCON BPS

Kind regards
Dawid

Something was definitely changed. I did not have thousands of unread elements in my Outlook feed.

Sounds like great news will have to check it out!

Hi,

the issue seems to be fixed. Our Power Automate flow just pushed a new entry to our Teams channel and there is no more an error opening the feed in the browser. Thanks a lot!

Kind Regards
Sébastien Anselment

Hi everyone,
From my perspective - setting up a report for a process is a must - you'll have to do it anyway, so creating a simple one for development purposes is not a time wasted, you'll have to do it anyway.
In the end, you can start sooner to think how end users will move around the app.

Most of end users which ended up in Searching structures asked if it's possible to hide it, so we're currently doing it as of 2025 it's possible to hide them completely.

My perspective on end users is just one company though, but as a dev i've never used it.