API access to a specific column value on an individual item with PHP

Hello there @netadmin_cf8594845 and welcome to the community!

If you use something like this, you should be able to get that data:

{
  items(ids: 1234567890) {
    name
    id
    column_values {
      text
      value
    }
  }
}

Take into account that some specific column types might require a different syntax. You can check how to get any column data here 😀

Matias,

Thanks! I actually figured out what I needed on this and couldn’t see a way to remove my post as it was still pending.

What I’m REALLY needing to know now is how to post a mutation query where I can create an item that includes a column value that is a pulse id column reference to another item on another board. I’m trying to make sure I have this in place so I can finish writing my integration for one of our systems I’m transitioning us from and really need to be able to create items that will have the right references in those columns.

For example, in this case, I’ve done a full import of our accounts into the crm side, but I’m wanting to tie our Contact records to the accounts as they are and I’ve got our source platform record id in as a column on the account board.

I’m reading a source contact file and then querying for the right item id from the account board based on that source platform id and it’s returning properly.

I’ve got absolutely everything working except the mutation. It looks like it tries to do it when I run my code, outputs the insert, but the insert is blank on the pulse id column still.

I’ve validated that the mutation is actually working though. It creates a new one any time I run it…so…

If you can help me with the best way to get the pulse id column reference to actually work, that would be awesome.

Thanks!

Hello again!

If I understand correctly, the item is created but without the value for that column.

Can you please send over the full mutation you are using? You can change the values a bit so that we don’t get the actual data you are using.

Looking forward to hearing from you!

Cheers,
Matias

Matias,

No problem. I’ve tried a lot of different variations and just can’t seem to get it to work.

Here’s an example.

mutation {
create_item (board_id: our_board_id, group_id: “topics”, item_name: “’ . $fullname . '”, column_values: “{"linkedPulseIds": {"linkedPulseId": "’ . $mondayid . '"}}”)
}

I’ve also tried to do it by column name (the linked column id is called contact_account), but I couldn’t get that to work.

Thanks!

Hello again @netadmin_cf8594845,

Would you be able to please try something like this:

mutation {create_item (board_id: our_board_id, group_id: "topics", item_name: "" . $fullname . "", column_values: "{\\"YOURCONNECTBOARDSCOLUMNIDHERE\\" : {\\"item_ids\\" : [\\"THEIDOFTHEITEMTOCONNECTTOHERE\\"]}}")
}

Let me know how that goes!

Cheers,
Matias

Matias,

I figured out what was wrong with my mutation. I had originally had the {id} in my original query from the docs but had removed it and once i added it back in, my queries are inserting just fine.

I do have one more question.

I’m curious if there is a particular way I need to escape and/or handle an email string for an email type column. I tried to include that in my new query and it’s not working with same escaping as the other fields. I can run the query with everything except the email string insert and it works fine. Is there something special I need to do with it to be accepted in the query?

Thanks!

Hello again @netadmin_cf8594845,

Can you please share the mutation that is failing with the email value you are using?

Sure.

Looks like the forum is removing the escaping for whatever reason when I paste, but this is the essense of what I tried.

mutation {
create_item (board_id: our_board_id, group_id: “topics”, item_name: “’ . $fullname . '”, column_values: “{"status": "Partner","text__1":"928 Santa Fe Street","text6__1":"’ . $mailingcity . ‘","text2__1":"’ . $mailingstate . ‘","text0__1":"’ . $mailingzip . ‘","contact_email": {"email":"’ . $email . ‘","text":"’ . $email . ‘","contact_account" : {"item_ids" : ["’ . $mondayid . '"]}}”)
{id}
}

Hello again @netadmin_cf8594845,

GraphQL wise, this syntax should work for you:

In a JSON this would look something like this:

I hope that helps!

Cheers,
Matias

Matias,

I figured out what the issue was with my email insert and have it working just fine now. Had to delete the stock phone and mobile columns and use text types for both as the default ones just didn’t want to work with any type of usage I tried on the insert, but I have it working now and I’m migrating our contacts over as I type this.

Excited to get our baseline in there and allow some of our users to hop in and start using the platform.

Thanks!

That is great news @netadmin_cf8594845 !

If you need anything you can always create a new topic here or fill this form to reach out to our technical support team!

Matias,

Is there no way to do an EXACT match query on a board item?

I’ve got our source system IDs stored on the account structure.

My code is doing a sampling query of 1 (I only want the exact match), but there could legitimately be two of the same id but still unique by…in this case…say the last letter of the id itself is lower and then upper on the second.

Two very distinct record ids, but when I query monday, I get a case insensitive result and with the sampling of 1, you can imagine that opens up a lot of opportunity for error on the connect column association.

I noticed the web UI search function does exactly the same thing…it’s doing a case insensitive search and returns multiple records instead of an exact match.

Is there no way to do that?

That will actually be really problematic for us if we can’t.

It will make moving to Monday a nightmare, honestly.

Here’s my query:

query {
boards (ids: our_board_id){
items_page (limit: 1, query_params: {rules: [{column_id: “text__1”, compare_value: [“’ . $accountid . '”]}], operator: and}) {
cursor
items {
id
name
}
}
}
}

Thanks!

Hello there @netadmin_cf8594845,

I see you asked this already here. I will check if there is a way of working around this to make it case sensitive and I will reply in the other topic 😀