Opiniones sobre Del análisis de macrodatos a un documento de Presentaciones

Minh D. · Se revisó hace alrededor de 6 años

Quan L. · Se revisó hace alrededor de 6 años

Duong T. · Se revisó hace alrededor de 6 años

Trân N. · Se revisó hace alrededor de 6 años

Very useful skills!

Fernando N. · Se revisó hace alrededor de 6 años

Rama L. · Se revisó hace alrededor de 6 años

Sridhar S. · Se revisó hace alrededor de 6 años

Kamil Z. · Se revisó hace alrededor de 6 años

John E. · Se revisó hace alrededor de 6 años

Kevin Jacob B. · Se revisó hace alrededor de 6 años

Bartłomiej B. · Se revisó hace alrededor de 6 años

Tomoya T. · Se revisó hace alrededor de 6 años

Tomoya T. · Se revisó hace alrededor de 6 años

Tomoya T. · Se revisó hace alrededor de 6 años

Mahmmoud M. · Se revisó hace alrededor de 6 años

Prof C. · Se revisó hace alrededor de 6 años

Sourav D. · Se revisó hace alrededor de 6 años

Mahmmoud M. · Se revisó hace alrededor de 6 años

Grzegorz W. · Se revisó hace alrededor de 6 años

Mahmmoud M. · Se revisó hace alrededor de 6 años

Mujib B. · Se revisó hace alrededor de 6 años

AUGUSTO ALONSO A. · Se revisó hace alrededor de 6 años

a y. · Se revisó hace alrededor de 6 años

Guys, this is the second time i do this lab and it's really bad bad written and super confusing lab. To start, it may be necessary to access gScript settings to turn on BQ API (i had to spend a lot time trying here and there until i find this was OFF). Then, it's really super super confusing all this wording. You guys may, for instance, take code lines to provide instructions as they move forward (place this code at line x because it will bla bla bla), or sketch where things goes in a map so people can figure it out the where things go and the why they need to be done that way. I place it amongst top 3 most frustrating labs i've ever done. Thanks. ---- Gosh, i can't do a decent score in Next 20 with this lab. More inputs: This is where things start to get out of track. What the hell do you guys mean with "tweak app"??? 2. Return spreadsheet: In the above code, createColumnChart() needs the spreadsheet object, so tweak app to return spreadsheet object so it can pass it to createColumnChart(). After logging the successful creation of the Google Sheet, return the object at the end of runQuery(). Replace the last line (starts with Logger.log) with the following: --- Isn't logical segregation so fancy and cute??? 3. Drive createBigQueryPresentation() function: Logically segregating the BigQuery and chart-creation functionality is a great idea. Create a createBigQueryPresentation() function to drive the app, calling both and createColumnChart(). --- What log line? No one read about a "log" immediately previously to this to be written. Why not include this instruction a couple paragraphs before, where changes already affects the logger.log line? To make runQuery() more digestible for general use, move that log line. The best place to move it? If you guessed createBigQueryPresentation(), you'd be correct! --- At this moment in time, there are 2 createColumnChart() functions: one at createBigQueryPresentation() function (Runs a BigQuery query, adds data and a chart in a Sheet) and another one in the createColumnChart(spreadsheet) function (Uses spreadsheet data to create columnar chart)... where it goes? All of the work on the slide deck takes place in the createSlidePresentation() function, which you add to bq-sheets-slides.gs right after the createColumnChart()function code. --- When i land here: 2. Add data table: The next step in createSlidePresentation() is to import the cell data from the Google Sheet into our new slide deck. Add this code snippet to the createSlidePresentation()function: I'm so damn furious of this lab that i just wanna puke ! --- On this one, you guy have a closing parenthesis: 3. Import chart: The final step in createSlidePresentation() is to create one more slide, import the chart from our spreadsheet, and return the Presentation object. Add this final snippet to the function: But you don't have an opening one :)))) --- on this instruction: 5. Update createBigQueryPresentation(): Since createColumnChart() returns the chart, you need to save that chart to a variable then pass both the spreadsheet and the chart to createSlidePresentation(). It funny because it's an instruction that operates over a previous instruction (the one to add the Logger.log). You guys are genious of this world. Can't this be simplified???

Américo A. · Se revisó hace alrededor de 6 años

Irene T. · Se revisó hace alrededor de 6 años