beast mode processing limitations

user095459

Our Domo instance is limited with federated data, but I noticed I can create case statements in beast mode to create a new field with associations with case statements. For example, I can map customers to an account manager with a statement, e.g. (CASE WHEN `Customer` = 'Joe Harris' THEN 'Mark Smith'), and I can use that beast mode in domo to manage around associations. I was able to get it to work with a sample of like 10, but when I tried to run around 1600 case statements, it timed out. I'm guessing its simply too much processing, but it doesn't give me any error to know for sure. I welcome any thoughts.

MarkSnodgrass

That's a pretty large case statement. I would suggest create a lookup table in a web form or Excel file and then join it to your main dataset in a Magic ETL dataflow. This will process much faster and be easier to maintain.

GrantSmith

@MarkSnodgrass, Federated datasets can't be utilized in an ETL.

https://domohelp.domo.com/hc/en-us/articles/360042932974-Using-the-Federated-Data-Solution#1.2.

@user095459

There shouldn't be much of a performance hit from a Domo standpoint. Do you have access to your database logs to see if your server is able to handle processing your query?

https://domohelp.domo.com/hc/en-us/articles/360042932974-Using-the-Federated-Data-Solution#5.0.0.4.

jaeW_at_Onyx

@user095459 recall. with Federated Query domo is passing the lift of processing the query back to your source system. This is no longer an Adrenaline question.

This is a Your Database question. The Federated Query Adaptor will have timeout rules etc built into it's configuration, that may be what you're running into.

That said, talk to your CSM and ask what your options are. With the new Data Fabric option, it theoretically should be possible to do ETL into your DataCenter (per @MarkSnodgrass 's idea)