Vid Pid Lookup
Placido Teofilo
I have multiple tables, some that have some information needed for a different table. I was thinking of using, lets say column A & B in Table One .I want to do a lookup to link Table One: Column A with Table 2 (different table): Column B.
So the idea is that Table 2: Column B has the master list, while our TABLE ONE is tied to that specific column. Right now I can only tie to a table and use the primary column of data. Any suggestions?
Nothing appears in the box. Could it be to do with that there will be more than one entry for related record for table b? Ideally i'd like it to show the newest entry added to table b for the related record.
You might want to check out the formula field and apply as a Text Area... The formula fields are still in preview but my quick test worked as expected (although I did not have a lot of rows of text. It did respect the layout including CR/LF etc.
It looks like the issue i have is that i need the lookup to look up multiple lines of text. The column that I'm trying to look at is paragraphs of text so it looks like this way won't work. Is there another way of doing it? I need the column from table a to have the data from table b in so when i pull out reports, it populates table b's data.
I've added a lookup column to Table A which looks up Table B. Now when i add a new column I'm unable to choose any columns in Table B for a formula or calculated column. I only see the table, not the columns within the table as choices. Any ideas? Thanks.
Hi my org does school lessons, we have lessons, teachers (who host the lesson), and our educators (who deliver the lesson). These are spread across 3 tables, with lessons having links to an educator and one or more teachers. I want to calculate the number of unique teachers an educator has reached. So I created a rollup field on the educator that uses COUNTA(ARRAYUNIQUE(values)) on the lesson's teachers. This works great if each lesson only has one teacher. But some lessons have multiple teachers, I tried a workaround using a lookup field and then a formula using ARRAYUNIQUE but that didn't work, as apparently the array formulas are just for rollup operations. Is there a workaround?
If you've got automations to spare you might want to just:
1. Add a linked field to your "Educators" table to the "Teachers" table
2. Add a lookup field to grab all the teachers this educator has ever interacted with
3. Add an automation that triggers when the lookup field is updated, and pastes the lookup field values into the linked field to the "Teachers" table
This will automatically generate a unique list for you:
I've banged my head against this wall for awhile now and couldn't figure out a formula based solution sorry
> I was trying a rollup with COUNTA(ARRAYUNIQUE(values)) which was giving 4 when it should be 5, but switching it to ARRAYUNIQUE(values) seems to give an accurate list: "Teacher 1, Teacher 2, Teacher 3, Teacher 4, Teacher 5"
One thing to note here is that I think that this might break if you have the following:
Thank you so much for looking into it, I too spent an hour trying different formulas because the correct string is RIGHT THERE. But I assume although it's showing "Teacher 1, Teacher 2, Teacher 3, Teacher 4, Teacher 5" it's actually ["Teacher 1", "Teacher 2", "Teacher 3", ["Teacher 4", "Teacher 5"]]. I will try an automation but this has to run on 3000 records so I'm a little nervous about it.
> I will try an automation but this has to run on 3000 records so I'm a little nervous about it.
Ah, for existing records just copy and paste the values in manually? Click on the "Teacher" lookup field header to select the entire column, copy, paste it into the "Teachers" linked field?
The automations would only be needed for when you create new "Lessons" records
> And by that last part do you mean that the COUNTA(ARRAYUNIQUE(values)) breaks if you have multiple teachers per lesson?
Yeah, I wasn't able to get it to give me the results I expected there
We are a beverage manufacutrer. We make and sell, soda, juice, cider, wine and beer - We separate customers by Alc & non-alc.
I have a SKU source with colour coded categories for each beverage. The intricacies are many here, but all I ask for is a unique option for lookup fields so identifying data is easily visible (category being one of them). I have automations to spare, but it's not a sustainable solution and it makes the base too reliant on me.
If I need to implement this elaborate automation workaround for each instance where I need this solution, I don't feel like I'm practicing no-code no more. I was hoping the airtable team would stay aware of this missing functionality. By marking this question resolved, I'm afraid they consider this problem solved.
When using the lookup command, if an OUTPUT or OUTPUTNEW clause is not specified, all of the fields in the lookup table that are not the match fields are used as output fields. If the OUTPUT clause is specified, the output lookup fields overwrite existing fields. If the OUTPUTNEW clause is specified, the lookup is not performed for events in which the output fields already exist.
When you set up the OUTPUT or OUTPUTNEW clause for your lookup, avoid accidentally creating lookup reference cycles, where you intentionally or accidentally reuse the same field names among the match fields and the output fields of a lookup search.
For example, if you run a lookup search where type is both the match field and the output field, you are creating a lookup reference cycle. You can accidentally create a lookup reference cycle when you fail to specify an OUTPUT or OUTPUTNEW clause for lookup.
If you are using the lookup command in the same pipeline as a transforming command, and it is possible to retain the field you will lookup on after the transforming command, do the lookup after the transforming command. For example, run:
If you are running federated searches over standard mode Splunk platform federated providers, and you want to use lookup to enrich the results of a federated search, consider whether you want the search to be processed on your local federated search head, or on the remote search heads of the federated providers you invoke in your search.
Standard mode federated searches that involve lookups complete faster on average when the lookup portion of the search is processed on the remote search heads of the federated providers invoked in the search. However, the lookup portions of federated searches run on the remote search heads only when one or more of the following statements are true:
If you are using standard mode federated search, and you want to process the lookup on your local federated search head, apply local=true to the search. When you apply local=true to a federated lookup search, the following things happen:
Suppose you have a lookup table specified in a stanza named usertogroup in the transforms.conf file. This lookup table contains (at least) two fields, user and group. Your events contain a field called local_user. For each event, the following search checks to see if the value in the field local_user has a corresponding value in the user field in the lookup table. For any entries that match, the value of the group field in the lookup table is written to the field user_group in the event.
Use the table command to return only the fields that you need. In this example you want the product_name, VendorID, and count fields. Use the vendors_lookup file to output all the fields in the vendors.csv file that match the VendorID in each event.
In this example, CSV lookups are used to determine whether a specified IPv6 address is in a CIDR subnet. You can follow along with the example by performing these steps in Splunk Web. See Define a CSV lookup in Splunk Web.
Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.
While there are a variety of different HTTP, selection, and delivery methods that can deliver, publish, and act upon Posts, this group of REST endpoints simply returns a Post or group of Posts, specified by a Post ID. While simple, these endpoints can be used to receive up-to-date details on a Post, verify that a Post is available, and examine its edit history. These endpoints are also important tools for managing compliance events.
The Post lookup endpoint provides edited Post metadata. All objects for Posts created since September 29, 2022, include Post edit metadata, even if the Post was never edited. Each time a Post is edited, a new Post ID is created. A Post's edit history is documented by an array of Post IDs, starting with the original ID.
This endpoint will always return the most recent edit, along with any edit history. Any Post collected after its 30-minute edit window has expired will represent its final version. To learn more about Edit Post metadata, check out the Edit Posts fundamentals page.
c80f0f1006