Hi, I am trying to connect a Data Source to a WorkSpace but getting an error. I can see an error for the following API call

curl '<https://gdcn-optimus.openturf.dev/api/v1/layout/dataSources/ad6190d5-0735-4d74-8410-14748dac584d/physicalModel>' \

Error

{
  "detail": "Some of Entities with IDs: [Identifier(Categorization)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(Demographics)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(FanMaturitySegments)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(FileUpload_contacts)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(PostWiseLast7Days)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(activeContacts)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(contactSource)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(contactsState)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(countryPhone)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(customerAssets)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(daily_contact)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(emailAssets)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(emailDomain)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(emailFailures)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(emailSubjects)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(email_wise)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(fanDataRichness)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(journey_wise)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(journey_wise_SMS)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(landingpages)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(licensed)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(planUsers)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(productOrders)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(smsAssets)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(sms_stats)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(socialmediaaccountstokens)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(storeOrders)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_FanMaturitySegments)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_Fb_Last7Days)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_FileUpload_contacts)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_Instagram_Last7Days)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_LinkedIn_Last7Days)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_SocialPosts_Last7Days)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_Twitter_Last7Days)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_activeContacts)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_alerts)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_daily_contact)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_day_time)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_email_stats)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_email_wise)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_email_yearly_volume)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_fanDataRichness)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_fan_types)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_journey_wise)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_landingpages)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_licensed)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_licensed_master)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_planUsers)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_sms_stats)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_socialmediaaccountstokens)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_top10)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_trend_of_campaigns_journeys)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(v_whatsapp_stats)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(whatsappBilling)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d), Identifier(whatsapp_journey_wise)/DataSource(ad6190d5-0735-4d74-8410-14748dac584d)] are already stored in database.",
  "status": 400,
  "title": "Bad Request",
  "traceId": "40436681ed9d729e"
}

Hi Rishi, For the start, can you please confirm which CN version are you using?

Hi, we are using 2.5.1

do I understand it correctly that you are trying to connect data source to workspace with api? what steps are you taking before you get this error?

@Jan Kos - I’m simply connecting the data source from the UI and getting the error

Heya Rishi, if you're still at the stage of trying to connect a datasource, I would really recommend you first upgrade to a newer version. Even going from 2.x to 3.x is a large step in terms of improvements to GD.CN's performance and caching capabilities. More importantly, starting with version 3, the Physical Data Model has been deprecated to simplify dataset interactions, so the chances of you still seeing issues post-upgrade are very small.

But it is working with other dataset in the same Google Big Query project…why is it that i have issue connecting with this dataset?

Well, the errors would seem to suggest that there is pre-existing metadata for the datasource ID in question, and the conflict prevents the connection from being established.

@Radek Novacek - How do i find it? At least in the Data Sources i was not able to locate the same dataset connected already…Also in the past we were able to connect same dataset to multiple Data Sources

Hi Rishi, you could try to get the declarative layout of the data sources using this approach, to see if there is any potential discrepancy between the UI and the data stored - documentation 👀

Hi @Radek Novacek - I can see that there are tables that have the same name as the tables in some other datasets already linked…however i could see that multiple data sets have tables with same name, so in the past it wasn’t a problem…wonder if this is causing issue

I'll try to discuss this with someone from our dev team who has worked on the GD.CN implementation - though please keep in mind that, given how many versions you are behind, it's entirely possible that this could be something addressed by updating anyway 🙂 I'll check and let you know Rishi!

@Radek Novacek - Did you discuss this with dev team? Any solution?