Best Of
Re: Follower Count, Post count for Social connectors
@jakebutterfield I found the Facebook follower count connector. Facebook Connector > Report = Page Info > Field = Common THEN followers_count. You could setup a daily append magic etl to start a recursive growing dataset which would eventually get you months time series history.
Let me know if this works. I'll keep looking for the other platforms.
Re: Add Table Design Param to Allow Setting of Table Borders Color/Weight
100% agreed, this would allow for much more professional looking dashboards for our stakeholders.
rolyat
Re: Drill Down issue
Is your top level card a Pivot Table? Where are you clicking exactly to drill down? Do you have any filters on the top level card that come from Beast Modes rather than actual values from the dataset? These things can all affect how drilling works and yield different results. Something else that has often caused me headaches is that if your org has Fiscal Calendar enabled you need to ensure both the top level card and the drill path card have the same setting for it (either to use it or not), otherwise the drilling goes awry.
Re: Font color
Under general properties on the Table chart, you can set Show Negative Numbers in Red checked to make negatives red. Also you can use the color rules to always set your value as green. the negative Red should override the color settings.
See for reference
Re: Get MySQL on latest version
We absolutely hear this signal on MySQL 5.6. Here are a few thoughts on how we see things:
- The expressive power of SQL is great. We know some of you (or others in your org) prefer SQL to MagicETL tiles. (Often we do, too!) We don’t see the two as direct competitors, but rather as different tools for different people or use cases.
- To that end, we are working on a SQL tile for MagicETL. This brings the expressive power of SQL to MagicETL (beyond the existing formula tile). We anticipate starting a beta of this feature later this year. We are working on an “Open with MagicETL” option for MySQL and Redshift DataFlows to help you easily port any existing flows to MagicETL, as desired. (And also a “Save as…” option so you can easily create a copy for testing before migrating your production DataFlow.)
- The SQL support being added to MagicETL will introduce non-equi joins to MagicETL as well as richer windowing function support. Common table expressions (CTEs) will also be available. These address some of the main areas where MagicETL is not a viable option today. A JSON tile is also coming soon to MagicETL. We will be evaluating the opportunity to expose the power of that tile within the SQL syntax, as well.
- MagicETL has the benefit of running all of your transform steps in a streaming/parallel fashion as frequently as possible. This is one of the many reasons you see faster processing times with MagicETL. A full database like MySQL or Redshift carries additional overhead that isn’t necessary with MagicETL. So, if we can hit the mark with SQL in MagicETL, we feel like you can end up with the best of both worlds. Also, with MagicETL, the automatic optimizations within MagicETL will continue to work when using the SQL tile in MagicETL. That means current or future optimizations to reduce processing time will be available automatically without any additional effort on your part.
- For any remaining use cases that cannot be solved in MagicETL, we feel that Adrenaline DataFlows may be your best next stop. That said, we know there may always be a spot where MySQL best suits your needs. In that case, we think exposing a modern MySQL engine within MagicETL will provide a powerful experience. While moving data into a MySQL instance for tasks that can be accomplished using the native MagicETL SQL tile will typically perform more slowly (and likely disable automatic optimizations), we’d like to make it easy for you to make that choice and seamlessly move your data into or out of MySQL to accomplish any processing steps that you’d prefer to run there.
- In order to avoid breaking existing pipelines, if we were to provide a modern MySQL version in the current experience, it would likely be exposed as a version picker within the existing MySQL DataFlow UI. Our hope, though, is to simplify the experience by moving towards fewer engines and UIs to choose from for data transform needs.
- On the subject of security, every MySQL DataFlow today gets its own MySQL instance running in a sandboxed environment without network access. We recognize that MySQL 5.6 has reached end of life, but have taken steps to keep your data pipelines secured and running without interruption.
Re: Warning: Not all the data is shown | Calendar Card
I am having the same issue with a filter card (checkbox selector) and a very small number of possible values (only 8). It seems to be a bug that needs to be fixed, but playing with sorting and group by fields makes a difference. Here are all the options in my list:
If I just put in the list of items, it shows the warning that not all data is shown, although it is.
If I filter out the NULL values, it gives the warning and removes the NULL values.
If I sort it by the channel-platform field as well, even fewer values are displayed.
If I sort it by the COUNT of the channel-platform field, then the error goes away, with all values displayed (although the order might not be what I want in all cases with this method).
If I sort it by the channel-platform field, and group it by the COUNT of the channel-platform field, then the error goes away, with all values displayed (except the NULL values filtered out) and the order is what I want.
So, there are options, but it is not ideal.
steveh
Re: Multiple results encountered for same location in pivot table.
That is an odd error. I haven't seen that one before. I would using your Division field first and see if it produces results without an error. I would also try switching to a standard table and see if that works. You might also try removing Division out of the Sorting properties and replace it with your beast mode.
Hope this helps.
