Problem with DataTag Fields

(Perry Ismangil) #1

I’m trying to fill in a field for an organisation connected to a DataTag. I tried on creation, together with adding the tag - that failed.

Then I tried in the next task, after the organisation has been successfully created, using ‘update an organisation’ and that failed too: ‘The ID was not recognised’

What am I doing wrong?

(Steven Booth) #2

Hello Perry,

Thanks for your message.

Would you like to share your workflow with the community and I, and we’ll take a look at what’s happening.

You can share it by going to the top right on the workflow builder, and changing the ‘Private’ setting.

Thanks,

Steven

(Perry Ismangil) #3

Which brings me neatly to ask: what happens when I share a workflow?

What info is seen by whom? The logs might contain sensitive customer data for example.

(Steven Booth) #4

Hello Perry,

There’s some guidance when you go to share the workflow:

“Your workflow can be copied by anyone who has its sharing link. Connections and logs won’t be shared. However, we will share the names of tasks and settings (the inputs to your tasks). Make absolutely sure your workflow doesn’t include any sensitive information.”

If you’d prefer to private message me with your workflow, then please do that.

Thanks,

Steven

(Perry Ismangil) #5

Here it is:

(Steven Booth) #6

Hello Perry

Thanks for sharing, so I can see exactly what we’re trying to accomplish.

One thing I don’t get to see is the specific custom fields you set up. I did try to emulate exactly what you have there in own own account, and so far I’m getting success on adding the ‘Customer’ and ‘Active’ tags.

(I set these up in my Capsule account as DataTags.)

So let’s break this down a little more:

I’m trying to fill in a field for an organisation connected to a DataTag. I tried on creation, together with adding the tag… —>

Which field are you trying to fill - Is it a custom field?

How did it fail - did you get an error message in the logs?

Then I tried in the next task, after the organisation has been successfully created, using ‘update an organisation’ and that failed too: ‘The ID was not recognised’ -->

Running your workflow, I can see that the you’re passing {{capsule_add_an_organization.id}} to the Party ID field of the ‘Update an Organisation’ task. This is exactly correct - and again, results in a success when I run the workflow here.

Could you run this once more and confirm you have the same issue?

Thanks,

Steven

(Perry Ismangil) #7

Back on debugging this workflow.

When you add a DataTag on an organisation on CapsuleCRM, it has a custom field connected to it.

In my case, I have a custom field called Maintenance Expiry with a Date type linked to the tag Active

It is this field Maintenance Expiry that I’m trying to fill, unsuccessfully.

I tried two separate ways:

  1. Filling it at Add an Organisation task:
  2. Filling it in the next task, Update an Organisation

Both method failed with the error: The ID was not recognised

The Active tag is successfully applied in both cases if I leave the Maintenance Expiry field empty.

(Steven Booth) #8

Hello Perry,

Thanks for following up.

I’ve had a closer look at this issue, and it may be that ‘DataTags’ we’re made available through the Capsule API subsequent to our development of the service into Flow XO.

We’d need to make a change to the service in Flow XO for ‘DataTags’ to operate in the way you intend - I’ve made a note of the requirement. I’ll let you know if we make this change to the existing service, but can confirm it’s not on our near-term roadmap.

Thank you,

Steven

1 Like
#9

I Vote for DataTags development. They make organizing many fields way easier in Capsule.