Supporting live connections to cloud files (Box)

Aperta
#158 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
python
Ambito
tooling

Direzione di ricerca

Start by reviewing the published-workbook XML snippet in this issue and the document-api-python code paths for updating connections. Compare the Box live-connection structure with the server-client-python issue linked in the report. Done means establishing and documenting the minimum fields needed to update and republish this connection.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

connectorRequest

I have an issue with updating the connections to a workbook once I added a live connection to an Excel file via Box. I was using the Rest API v2.8 using server-client-python package have an open issue in that repo as well.

I am sharing what the xml snippet looks like in my published workbook for this connection to see if there's any modification that can be suggested to update the connection / traverse the ETree. What would be the bare minimum fields that need to be repopulated every time to publish to server, i.e. what is the Desktop client doing to the xml when we click publish with a live connection like this?

      <connection class="federated">
        <named-connections>
          <named-connection caption="Reporting_Commentary" name="cloudfile:box-excel-direct.1bk2zjd1uefpc71dfvxop1xj4y0b">
            <connection class="cloudfile:box-excel-direct" cleaning="no" cloudFileExtension="xlsx" cloudFileId="318391143483" cloudFileMetadata_-_folder="53478632394" cloudFileName="Reporting_Commentary.xlsx" cloudFileProvider="box" cloudFileRequestURL="https://api.box.com/2.0/files/318391143483/content" compat="no" dataRefreshTime="" filename="Reporting_Commentary.xlsx" interpretationMode="0" server="" server-oauth="server-custom" userLanguage="en" username="uname@example.com" validate="no" workgroup-auth-mode="prompt"/>
          </named-connection>
        </named-connections>
        <relation connection="cloudfile:box-excel-direct.1bk2zjd1uefpc71dfvxop1xj4y0b" name="Content" table="[Content$]" type="table">
          <columns gridOrigin="A1:D91:no:A1:D91:0" header="yes" outcome="6">
            <column datatype="date" name="Fiscal week start" ordinal="0"/>
            <column datatype="string" name="Aggregation" ordinal="1"/>
            <column datatype="string" name="Calculation Type" ordinal="2"/>
            <column datatype="string" name="Commentary" ordinal="3"/>
          </columns>
        </relation>
        <metadata-records>
        ...
        </metadata-records>
      </connection>
Lingua principale
Python
Stelle
363
Fork
183
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tableau/document-api-python

Tutte le issue di tableau/document-api-python

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.