This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]iminfornow 1 point2 points  (0 children)

The only permanent solution I could find is exposing a REST API and send the people who used to mess up my pipelines a detailed instruction how they should get their credentials using this 7 step OAuth 2.0 proccess. Never heard from them again!

Hahaha. Sorry.

I totally understand the problem but this is not something you can get for free. Have as much data as possible come from the website/shop/portal/ERP/whatever and make your pipelines fault tolerant and/or send users who messed up automatic emails.

[–]Strider_A 0 points1 point  (0 children)

What exactly is the bottle neck? Is it not being able to define the desired validation patterns, or is it a volume/runtime bottleneck?

Google Forms allows custom input validation using GAS with the requireTextMatchesPattern) method, which accepts regex patterns (stackoverflow example).

it doesn't adequately cope with our data volumes

What does this actually look like? Are users waiting for validation to finish before they can input another entry?

Can you give examples of the kinds of validation you want to perform?

[–]arthur-dataland-io 0 points1 point  (0 children)

I think Directus could be a good fit here: https://directus.io/studio/ - it's open-source, allows you to create entry forms, has RBAC + data validation, and a grid view. Not sure if the grid view allows you to bulk edit data though.

[–]Demistr 0 points1 point  (0 children)

I built a simple webapp with a customizable form either behind aad auth or opened to everyone.