ContributionsMost RecentMost LikesSolutionsRe: Google API QR Codes not working? My error/oversight. The google api has been decommissioned, I hadn't noticed. Posting my corrected code in case it helps anyone. Original <img src=\"https://chart.googleapis.com/chart?chs=100x100&cht=qr&chl=" & [SPARK Tracking #] & "\"></a>" Revised: var text data = [Spark Tracking #]; <img src='https://quickchart.io/chart?cht=qr&chs=150x150&chl=" & $data &"'></a>" Confirmed working as below: Google API QR Codes not working? Hi, has anyone else run into the issue this week where the QR generator at chart.googleapis.com has suddenly stopped working? Even my sample code of https://chart.googleapis.com/chart?chs=100x100&cht=qr&chl=HelloWorld is returning a 404 not found.... Re: Pipelines 'You are offline', not saving, and more Mike, just chiming in, my experience is verbatim what you have, and as you said, doubly frustrating as all things are being funneled to pipelines ------------------------------ Jeremy Myer ------------------------------ Re: Odd question looking for guidance Sam, I have found the same thing, I call it 'Zombie mode' where everything is appearing correctly, however the saving is prohibited. The embedded report/page is putting you in that state. If you look at the console, you'll see a warning notifying you of the conflict. QB knows about it and claims it's a safeguard for something....I can't recall what off hand Hope this helps ------------------------------ Jeremy Myer ------------------------------ Re: Phantom data appearing in 'new' embedded report My understanding is that there is a bug whereby this is actually working "correctly". I'd bet these 4 records shown do not have a related parent, or the related X is blank. Because this new record does not yet have a [record ID#], it is technically correct, in that [Record ID#] = 0 in all cases. The legacy report links masked out this situation somehow. My workaround thus far has been hiding this report until the record is saved. Janky, and doesn't work for every situation, but it does the job for me. ------------------------------ Jeremy Myer ------------------------------ Re: Possible to display another record, within current record? Chase, admittedly they have not been full code pages, they're native reports I've embedded, either on forms or dashboards. I've seen the code pages examples where we can make that work. This specific use case was a report that I wanted to use on a dashboard, without the header row and the wasted space on the left margin. The response below: When any save of a record is attempted, as Mike mentions in his response, we just get a spinning wheel & hung page. ------------------------------ Jeremy Myer ------------------------------ Re: Possible to display another record, within current record? Mike, just a curiosity, your embedded form, are you acting on it? Like buttons and other workflow-y things? I've run into a limitation in the past where the embedded form is great, but only for 'looking'. Any 'doing' gives me an error that for some reason QB disallows actions from within this embedded frame. ------------------------------ Jeremy Myer ------------------------------ Re: Vertical field elements in same row form Bob, I do this a lot, see example and code... ------------------------------ Jeremy Myer ------------------------------ Re: Programmatically Change Form Tab Color I'm opening in the same tab/window, making it feel to the user like a screen refresh, not a lot different to the native tab navigation. They only go back to the first 'tab' when they initially click on the record, or click on the first 'go button' I neglected to mention the fields above the 'tab row' is consistent within the sibling forms, so it also tricks the user into feeling just a screen refresh. ------------------------------ Jeremy Myer ------------------------------ Re: Programmatically Change Form Tab Color I made a workaround that my users like, for multiple reasons.... 1) You can't redirect/point to a specific tab, this solution does 2) You can't format the tab conditionally, this solution does. 3) You can't have multiple Tab rows, I haven't used this, but you could... a) I created a series of 'go buttons', arranged & formatted them to look like native QB tabs b) I created a series of forms (I know, maybe not best practice, but it works for us) c) each 'go button' loads a different form for that subset of fields d) I can conditionally vary the color, font, label, etc of the tab based on date or completion status or user permissions or whatever It may not work for all, but an option of how to get around this functionality gap... ------------------------------ Jeremy Myer ------------------------------