โ06-11-2024 06:19 AM
Our goal is to establish Integration A, which serves as a data repository. The data stored in Integration A is then utilized in another recipe, Integration B, to ascertain the appropriate endpoint for data transmission. What is the most effective method to accomplish this within Workato? The current proposal involves storing data in a lookup table. Are there any superior alternatives or recommendations
Solved! Go to Solution.
โ07-01-2024 06:39 AM
Because it doesn't share the same limit as a Lookup table. While the Lookup table maxes out at 10,000 records, aI'm not aware of a limit to the number of messages stored in a Pub/Sub Topic. It's essentially a message queue so it's designed to hold many messages to be consumed.
a week ago
@CodersArcade wrote:Our goal is to establish Integration A, which serves as a data repository. The data stored in Integration A is then utilized in another recipe, Integration B, to ascertain the appropriate endpoint for data transmission. What is the most effective method to accomplish this within Workato? The current proposal involves storing data in a lookup table. Are there any superior alternatives or recommendations
yesterday
In my opinion, Data Tables serve as a more robust and scalable alternative to Lookup Tables, especially for use cases involving larger datasets, complex filtering, or relational-like structures.
Below, Iโve outlined the key limitations of both Lookup Tables and Data Tables. Please review them to understand which option best suits your needs. If you need further assistance or a recommendation based on your specific use case, feel free to reach out.
yesterday
I agree that Data Tables are a better option now over Lookup Tables. At the time I wrote my original responses, Data Tables were tethered to Workflow Apps, thus an add-on to be bought. Within the last couple months I noticed Data Tables present and seemingly available to us, so I think there have been some licensing changes around that. So if they're available, then yes they can make more sense depending on the use case. Lookup tables are really meant more for quick translations of values rather than data storage
 
					
				
				
			
		
