#Pega

[@akhilbunny6639]

Helpful!

[@HarshaTrainingsacademy]

Glad it was helpful!

[@arjun0able]

Why we need two data pages here Search and result data pages ? Instead of calling two D_page is it possible to have one D_page and execute the result ?

[@KumarSK-w7q]

Hi Harsha, first of all, thanks alot for the explanation that every one can understand. Became a fan of your videos. I have a query on keyed data page. I would like to understand the benifit of using Keyed Data page over a parameterized data page of structure List and with scope as Node, as this will also fetch the data once and place it in clipboard. I will use the parameterized data page as source to grid and keep the visisbility condition as entered CustonerID matches with CustonerID in data page results. In this case also the data hit will not happen. Please correct me if i miss anything.

[@HarshaTrainingsacademy]

Hello! I'm glad to hear that you find the explanations helpful, and I appreciate your kind words! Let's delve into the topic of Keyed Data Pages in Pega and discuss their benefits compared to parameterized data pages with a list structure. **Keyed Data Pages:** A Keyed Data Page is a specialized type of data page in Pega that is designed to store information in a hierarchical structure, where each instance is uniquely identified by a key. The key could be a property value, such as a customer ID in your scenario. **Benefits of Keyed Data Pages:** 1. **Single Fetch for Specific Instance:** Keyed Data Pages allow you to fetch a specific instance of data based on a key. This is advantageous when you want to retrieve a particular record without fetching the entire dataset. 2. **Automatic Caching:** Keyed Data Pages automatically cache the fetched instances. If the same instance is requested again, it is retrieved from the cache instead of making a redundant server call. 3. **Efficient Memory Usage:** Keyed Data Pages efficiently use memory because they store only the instances that are requested. This is particularly useful when dealing with large datasets, as you only bring into memory what is needed. **Parameterized Data Pages with List Structure:** Parameterized Data Pages with a list structure are suitable when you need to fetch a set of data based on specific criteria, and you don't necessarily have a unique key for each instance. In your case, using a parameterized data page as a source for a grid with a visibility condition is a valid approach. **Considerations:** 1. **Data Granularity:** If you need to work with individual instances based on unique keys (like customer IDs), a Keyed Data Page is more suitable. If you are working with a set of data that doesn't have a unique key, a parameterized data page with a list structure might be more appropriate. 2. **Performance:** Both approaches can be performant, but the choice depends on the specific use case. Keyed Data Pages are optimized for fetching specific instances efficiently, while parameterized data pages with lists are optimized for fetching sets of data. 3. **Memory Usage:** Keyed Data Pages may be more memory-efficient for scenarios where you're dealing with individual instances. Parameterized data pages with lists might consume more memory if you're dealing with large result sets. In conclusion, both approaches have their use cases, and the choice depends on your specific requirements. If you need to work with individual instances identified by a key, a Keyed Data Page is a good choice. If you're working with sets of data based on criteria, a parameterized data page with a list structure is appropriate.