Unanswered questions

Hi,We are currently using TX 20.10.80.64 in combination with TX Data Enrichment. TX DE is exposed as a source in the ODX.When we modify a Custom SQL query via Table Designer → Actions → Source, it appears that the data is not refreshed in Home afterwards. Old columns or outdated row counts are still displayed.We have configured primary keys (PKs) to define the columns in the Table Designer.Therefore, we suspect that when we call the ODX source TX DE within TX 20.10.80, the data is not being refreshed from TX DE.What are we doing wrong?

Hello,Since about a month ago, I am not able to connect to Sharepoint Lists anymore. When I test the connection, I get the error message as seen in the image below. Authentication wise, I use Auth scheme AzureAD end the Sharepoint edition is Sharepoint Online. I do not use OAuth and I am able to login to the Sharepoint site with the account I use. Is anyone experiencing the same issue or does someone know how this can be solved? 

After upgrading to Ingest 7313.1 I updated my REST API provider version to 12.1.0.0. Now some of my REST endpoints have started failing.Running “Import metadata” works fine, but when it tries to extract values from the JSON, it fails with errors like: Failed to execute callback for endpoint 'Get Charge Points':Column 'data_id' does not belong to table charge-points.System.ArgumentException: Column 'data_id' does not belong to table charge-points. But it should be able to parse it.The structure of the JSON is like this (just showing top of file):{  "data": [    {      "id": 1096237,      "teamId": 449574, Any tips? 

See the below screenshot.  I’ve installed Classic 26.2.1.1 and if I just put in the License Key, it tells me I need to have an activation file.  Never had to do this with 20.10.Went to download the activation file, and there is not an option for v26.  If I try a 20.10 activation file, it says it’s the incorrect version.Using the Alithya partner key starting with: 3c67…. 

In TX Enhanced Connector, how do one handle fields in JSON response that has the same name?In the screen-grab below, the fields in marked in red comes multiple times but the values are different.In TX Enhanced Connector, the field always grabs the value of the first occurance of the field i have marked in red.Is there a way to grab the desired value by doing somethng like this:/json/addendumValues/addendumGroups/rows[0]/json/addendumValues/addendumGroups/rows[1]/json/addendumValues/addendumGroups/rows[2]/json/addendumValues/addendumGroups/rows[3] If not, is there a way to grab everything in blue and show in one column?I can then creat a view in BU and grab each saperately The screen grabs are broek here: Understanding and using script parameters in TimeXtender Classic | Community, so i can not fuly understand the documentation

Can I preserve my source field names when synchronizeing my fields?I dont want spaces and periods replaces by an underscore, my current workaround is to edit the fields manually when I use the tables in my prepare instance.  

I believe I have read the documentation, in case I missed something. My bad. Im trying to load csv files from the root of a S3 bucket. The 'test connection’ in the portal turns green but when trying to synchronize in timextender it tells me I have to enter a value for ‘path’.I have tried these so far: /.mybucketname/inbound/s3://mybucketname/inbound/But timextender keeps throwing errors saying the directory does not exist. I can succesfully connect to it and download the csv's via Python so Im quite sure the setup is correct.  Does anyone know what to fill in for ‘path’?

We are getting a bad request error when we are using the timextender odata data source.  When we use the endpoints that we previously selected during metadata discovery, they still work normally. So why is the discovery metadata at the moment not working (it worked the first time). Thank you in advance!   

Hi all,I am looking for architectural advice on designing a future-proof multi-ERP data warehouse setup in TimeXtender.We currently have multiple ERP systems feeding into one data warehouse. The goal is to create a scalable pattern that works now, but also remains maintainable when more ERP systems are added later.The main question is around where and when to create keys, especially super natural keys / business keys, and where to perform the joins between facts and dimensions. I found some scattered articles on keys and stuff, but not really an proposed best practice in TimeXtender. I understand there are multiple ways to Rome depending on the setup/preferences/performance etc. but I reckon there would be an advices standard based on TimeXtender working and fundamentals. Example simplified architecture:DSA.ERP1.Customers- CustomerID- CustomerName- DW_SourceCode- SNK_Customer = DW_SourceCode + CustomerIDDSA.ERP1.Invoices- InvoiceID- CustomerID- Amount- DW_SourceCode- SNK_Invoice = DW_S