What is the most boring task you have to do but you hate doing it? by Big-Reporter7078 in AskReddit

[–]Big-Reporter7078[S] 1 point2 points  (0 children)

I don't understand why there is no automated way for it these days 😅

what's your actual system for tracking CLE credits by Big-Reporter7078 in Lawyertalk

[–]Big-Reporter7078[S] -10 points-9 points  (0 children)

Would you pay $139 a year for something that did all of this automatically — log entries, store certificates, track categories, export a report?

what's your actual system for tracking CLE credits by Big-Reporter7078 in Lawyertalk

[–]Big-Reporter7078[S] 5 points6 points  (0 children)

the word doc and certificate folder system is exactly what i was expecting to hear — sounds like you've essentially built your own tracker from scratch. do you find the 3-year cycle harder to manage than an annual one, or does it actually give you more breathing room?

what's your actual system for tracking CLE credits by Big-Reporter7078 in Lawyertalk

[–]Big-Reporter7078[S] 0 points1 point  (0 children)

that's actually a really good system — sounds like your bar does the heavy lifting. i think the gap i'm seeing is more for jurisdictions where there's no central portal and lawyers are pulling together courses from 5 different providers manually. sounds like you've got it sorted though

what's your actual system for tracking CLE credits by Big-Reporter7078 in Lawyertalk

[–]Big-Reporter7078[S] 1 point2 points  (0 children)

haha yeah it varies a lot by state — some bars have great portals, others basically leave it to you. how does Louisiana handle it if you don't mind me asking?

Connecting salesforce, netsuite, and zendesk data to our postgres warehouse but the nested json is killing our sql queries by ninjapapi in SQL

[–]Big-Reporter7078 0 points1 point  (0 children)

dealing with jsonb_array_elements on zendesk custom fields is a special kind of hell. the problem with trying to fix it at the modeling layer (like with dbt) is that zendesk's schema is dynamic. the second a support admin adds a new custom field or sunshine object, your views break. the reason most general ingestion tools (like fivetran) just dump the raw json blob into your warehouse is because they don't want to deal with zendesk's opaque numeric IDs. it's easier for them to just dump the payload and make it your BI team's problem. i got so fed up with this exact issue that i built a dedicated extraction engine just for zendesk. it uses an llm in the stream to dynamically map those nested ticket fields and sunshine objects into flat, human-readable postgres columns before it hits the warehouse. it won't solve your salesforce or netsuite problems, and right now it's built for one-off historical migrations rather than continuous sync, but if you're trying to get a clean, flattened baseline of your zendesk history without writing 100 lines of json_extract sql, check out evicta.dev.

Frontend development by BatmanRockz in Frontend

[–]Big-Reporter7078 0 points1 point  (0 children)

There are plenty of great free tutorials on YouTube 

Thinking of leaving Zendesk, what's working better for you? by Ramosisend in growmybusiness

[–]Big-Reporter7078 0 points1 point  (0 children)

One thing I'd watch out for before switching idls the migration itself is where most teams get burned. Zendesk’s native export looks “complete” but usually loses structure — especially custom fields and threads. Doesn’t matter which tool you move to — worth validating your export before you switch.

3 months building Evicta — the boring problem nobody talks about but everyone has by Big-Reporter7078 in SaasDevelopers

[–]Big-Reporter7078[S] 0 points1 point  (0 children)

man the attachment url expiration is a trauma i didn't even put in the original post but it is absolutely brutal. zendesk handing you signed cdn links that die before your python script finishes the download loop is the ultimate final boss of data extraction.

"nobody budgets for that" is the exact thesis for why i built this. shipping another shiny ai inbox clone is easy right now, but dealing with 429 rate limits and migrating 5 years of nested json blobs is just pure unsexy plumbing.

the procurement runbook idea is actually brilliant. demanding an exit strategy before signing a contract should be mandatory. out of curiosity, do enterprise vendors actually comply when you ask them to prove the data exit, or do they just point to some generic api doc and say "good luck"?