I’m working on publishing a Portal, and I’m seeing this warning:
Incompatible plug-in(s) detected. Refactor the portal object precedents to only use plug-ins compatible with portals. Using incompatible plug-ins can cause the published portal to error. Precedent(s) containing incompatible plug-in(s).
Has anyone dealt with this before?
What are the recommended alternatives for Excel Tools functions (like reading/writing Excel, parsing uploaded files, or exporting data) that work in Portals?
Are there any Appian-native approaches or other supported plug-ins I can use instead?
Would shifting the Excel logic into a process model (triggered from the Portal) be a valid workaround?
Any best practices or migration tips would be greatly appreciated.
Discussion posts and replies are publicly visible
The appian-native approach you would need to consider is a Web API and/or a Start Process call, and in either case you would configure it such that it launches a process model, which can then utilize whatever plug-in (or other smart services) you want, then pass the result back to the Portal form.