Currently, XM Solutions only support these resources. We’re working on adding more resources as time goes by, but please enter your idea in Evolve (the Ideas section here in XM Community) so we can keep track of interest.
For now, you’ll have to remove anything xFlow related.
Thanks!
@romeoT I had this same problem just today. I was wondering if something was out-of-date, but it doesn’t appear to be so.
@qHubert I’ve been able to complete build on a solution before, but this is the first I saw this same error. Did something get changed recently? I thought the solution I’m trying to build on is similar to a solution I configured in the past and had a successful build on, but I’m not 100% positive.
Ah, never mind. I was conflating. The previous solution I’d been working on (but temporarily shelved) DID have a successful solution build, but it was operating off a solutionExecution.json that didn’t have any task.v0 or trigger.v0 items.
The one i tried today was the first solution I’d tried with a solutionExecution.json file containing task.v0 and trigger.v0.
Of note, the solutionExecution.json file stemming from the import of a survey resource doesn’t contain those problem items. The solutionExecution.json file stemming from the import of a CXDashboard resource DOES contain those problem items.