malformed ID ‘’.
The remote server returned an error: (400) Bad Request.
it worked for a while, but now it gives this message.
I created a view on Simplicate system, and I would like to run that view.
Here it is:
create view Companies as
select *
from Simplicate.CRM.Organizations ORG
Left join Simplicate.CRM.OrganizationCustomFields CF1 on CF1.name = "group_name" and CF1.id_1 = ORG.ID
Left join Simplicate.CRM.OrganizationCustomFields CF2 on CF2.name = "group_number" and CF2.id_1 = ORG.ID
Left join Simplicate.CRM.OrganizationCustomFields CF3 on CF3.name = "engagement_partner1" and CF3.id_1 = ORG.ID
Left join Simplicate.CustomFields.CustomFieldOptions CF4 on CF4.ID = CF3.value
Do you have any idea what can be the problem with that?
create view Companies as
select *
from Simplicate.CRM.Organizations ORG
left
outer
join Simplicate.CRM.OrganizationCustomFields CF1
on CF1.name = 'group_name'
and CF1.id_1 = ORG.ID
left
outer
join Simplicate.CRM.OrganizationCustomFields CF2
on CF2.name = 'group_number'
and CF2.id_1 = ORG.ID
left
outer
join Simplicate.CRM.OrganizationCustomFields CF3
on CF3.name = 'engagement_partner1'
and CF3.id_1 = ORG.ID
left
outer
join Simplicate.CustomFields.CustomFieldOptions CF4
on CF4.ID = CF3.value
Invantive SQL rewrites such a query, depending on the volume of data and capabilities of the backing problem. For instance, when there is just one or a few possible values for CF3.value, the software will internally rewrite the query on CustomFieldOptions to:
select *
from CustomFieldOptions
where ID in ('val1', 'val2', ..., 'val9')
This ensures the fastest real-time response time, reducing some queries that would run for hours when retrieving all data first to seconds by very selective filtering.
However, probably the Simplicate API didn’t understand the query or the Simplicate-driver issued a wrong API-call.
Can you reproduce the error and add an answer with the following information:
date/time of occurrence in UTC or CET timezone (specify timezone),
full error message include error code (like “itgenxxx999”).
Using that information it should be possible to find the error message and the related information, and provide better guidance, a workaround or a bug fix.
This question was automatically closed after at least 2 weeks of inactivity after a possible solution was provided. The last answer given has been marked as a solution.
Please ask a new question via a separate topic if the problem occurs again. Please include a link to this topic in the new question by pasting its URL into the text.