ArborRose Coach

コメント

  • I liked the JSON OAuth connector also, but dislike the speed. I found that using a different method with Jupyter notebooks and Python, I have more flexibility talking to my APIs and my speed is significantly faster.
    JSON Dynamic Body ArborRoseによるコメント August 2024
  • Enthusiastic "yes".
  • 1. Timing/Latency Issues with Input Datasets Problem: If the input datasets are updated by upstream processes (e.g., data imports, other ETLs, or connectors), there might be a timing issue where the ETL is triggered before these datasets are fully refreshed or populated. Solution: Adjust the schedule of your ETL to run…
  • Have you checked the dataflow schedule? Make sure the dataflow is scheduled to run regularly. Sometimes, the dataflow may not be set to refresh automatically, which would cause the input data to lag behind the source table. (Let us know if you need some assistance understanding how to check or setup the schedule.) Domo…
  • One way to do it might be to organized columns: Referer, January, February, March, April, May…. Create calculated fields for month to month changes. Such as CASE WHEN `February` > `January` THEN 1 WHEN `February` < `January` THEN -1 ELSE 0 END And create similar calculations fields for every month pair. Then set up…
  • The 401: Unauthorized error you're encountering typically points to an authentication issue. Expiration - The OAuth token used by the Domo GA4 connector may have expired. Insufficient permissions - The Google account used to authenticate with the GA4 API might not have sufficient permissions to access the requested data.…
  • I don't know the version, but it's this thread and Andrea's comments may answer your question.
  • To transform your dataset, use Magic ETL. Setup selected columns. Add an Unpivot Tile. Drag the Unpivot Columns tile onto the canvas. Unpivot Columns: Select budget, forecast, and actuals. New Column for Key Names: Enter Category. New Column for Values: Enter Value. This will turn the three columns into two: Category and…
  • If you transform your dataset Category Value Type Budget 343 planned Budget 3432 carry-over Budget 123 unplanned Forecast 444 planned Forecast 4432 carry-over Forecast 145 unplanned Actuals 200 planned Actuals 3302 carry-over Actuals 80 unplanned Then create a stacked bar using category on the xaxis, value on the yaxis,…
  • from domomagic import * import pandas as pd # Reading the data from Domo input1 = read_dataframe('Existing - Sales Rev') # Convert input to a DataFrame df = pd.DataFrame(input1) # Sort the DataFrame by 'Close Date' df = df.sort_values(by='Close Date') # Initialize a set to keep track of seen accounts seen_accounts = set()…
  • Try this: from domomagic import * import pandas as pd # Reading the data from Domo input1 = read_dataframe('Existing - Sales Rev') # Sorting the DataFrame by 'Close Date' df = input1.sort_values(by='Close Date') # Initialize a set to keep track of seen accounts seen_accounts = set() # Initialize a list to store the results…
  • I should have noted that my legend shows in order of outer ring to inner ring. Labels on the rings are not turned on in the screenshot.
  • This is a bit out of my area of reach, but I'll give it a go. Based on what I read and see in your image, it looks like you are working with a brick that involves making an API call to a Domo dataset. Then performing calculations, and possibly aggregating data with subtotals. To calculate subtotals and a grand total using…
  • If you are trying to capture other titles that include accented characters, the following might work. CASE WHEN Page Title REGEXP '^[A-Za-zÀ-ÿ0-9 .,!?-]*$' THEN 'English' ELSE 'Other' END This would cover most accented Latin characters used in European countries. Basic Latin alphabet characters (A-Za-z) Accented characters…
  • I'm not sure if I understand your description or your data well enough, so this may be off track. But perhaps enough to assist. if you have a calculated field like this (z_Combined_Units): CASE WHEN `Unit Type` = 'Climate Controlled' THEN `Climate Controlled` WHEN `Unit Type` = 'Drive Up' THEN `Drive Up` WHEN `Unit Type` =…
  • Filtering on multiple keywords can be tricky. You can set a column on the dataset to match the condition(s) you require. Or create a filter formula: CASE WHEN `column_name` LIKE '%keyword1%' OR `column_name` LIKE '%keyword2%' OR `column_name` LIKE '%keyword3%' THEN 1 ELSE 0 END
    Filtering a card ArborRoseによるコメント August 2024
  • Are you sure its referring to the output dataset? Does your SQL have input datasets that may be locked?
  • I don't do much with Smart Text but I think you'd need to create calculated fields to dynamically calculate the start and end dates with a label for the period you need. Start Date of Last Week: DATE_SUB(CURRENT_DATE(), INTERVAL (WEEKDAY(CURRENT_DATE()) + 6) DAY) This calculates the Monday of the previous week. End Date of…
  • I don't know a specific chart type if custom formatting isn't available. I don't know all the options without trying to replicate the entire thing myself and see what's available. My approach would be to start creating some kind of custom output using a brick or possibly try to work with separate charts in a dashboard…
  • Can you reformat the JSON incoming, before you handle it? Loop through each object in the array, extracting the details from the "name" key and creating a new object with the key "details" associated with the value. // Simulating the incoming invalid JSON (you receive this from the API) var invalidJson = [ { "name":…
  • That's too bad. And you can't go back to the source of the API code and talk to them about it?
  • If you're applying this Beast Mode calculation to a chart, ensure the chart type is compatible with mixed data types, as some chart types may not handle string formatting (e.g., concatenating a %) on axis values. 1. Beast Mode Calculation with Mixed Data Types If your Beast Mode calculation returns different data types…
  • Given a structure: { "name": ["details1"], "name": ["details2"], "name": ["details3"], "name": ["details4"] } This JSON structure is not valid because JSON keys must be unique within the same object. If your data is like this: [ {"name": "details1"}, {"name": "details2"}, {"name": "details3"}, {"name": "details4"} ] You…
  • If your screenshot is showing a card with a dropdown filter, the card would have the field/column at the top in items and optional group. Go to the optional group and set the format as number and uncheck the thousands separator box. Result:
  • 1. DataFlows: Data Storage: Yes, DataFlows (which include Magic ETL, SQL DataFlows, and Python/R DataFlows) store the output datasets in the Domo cloud. When you run a DataFlow, it processes the data and outputs the result as a new dataset in Domo, which is stored in the Domo cloud. 2. SQL View (Domo): Data Storage: Yes,…
    Data storage ArborRoseによるコメント August 2024
  • How about CASE WHEN `Churn Unit` = '% of Units' THEN CONCAT(ROUND(`Churn (%)`, 1), '%') WHEN `Churn Unit` = '# of Units' THEN ROUND(`Churn (Units)`, 0) END ROUND(Churn (%), 1): Rounds the churn percentage to one decimal place. CONCAT(ROUND(Churn (%), 1), '%'): Appends a percentage sign to the rounded percentage value to…
  • The issue in your JSON code seems to be the repeated "name" keys without nesting. To properly reference the data in your loop, you should ensure that each entry in the array is an object with distinct keys for "name" and "details". JSON [ {"name": "details1", "detail": "detail1"}, {"name": "details2", "detail": "detail2"},…
  • To compare month to a previous year's same month: sum( case when YEAR(`transaction_entry_date`) = YEAR(DATE_ADD(CURRENT_DATE(),-365)) and MONTH(`transaction_entry_date`) = MONTH(DATE_ADD(CURRENT_DATE(),-365)) and `date` <= DATE_ADD(CURRENT_DATE(),-365) then `amount` else 0 end And add a criteria such as Month(date)=1 if…
    YTD, YOY, M-1 ArborRoseによるコメント August 2024
  • Something to ponder
  • It sounds like you are encountering different levels of aggregation - the left table and the right table aren't matching correctly. Make sure the tables are aggregated consistently, and that the data formatting match. If there are duplicate 'Project ID' values in the left table and not in the right table, you will get…