ContributionsMost RecentMost LikesSolutionsRe: Could not parse XML inputHi Austin, Thank you very much for analyzing the problem. Thanks! I am not comfortable with JS. I've asked a friend to help me, in your way. We don't have enough time to dig deep. But we are close. It seems that the code can't read the model record ID#, or can't create a new ID#. ..............Something is wrong here. We will keep looking it over the weekend and hope to solve it. Re: Quickbase connected table - changing refresh keyAny solution to this issue?Quickbase Connection IssueI have been trying to switch a connection to a connection I own. However, I keep getting an error showing that I am trying to connect to a different table than the one in the connection I own. The table ID referenced in the error is in a completely different app and I am not sure if this could be that the previous owner used to have a field that connected to that table. That app's table referenced in the error message had a name similar to the name in the app I am trying to connect and I am wondering if this could be the issue. Is there a way to edit the connection and see the table being connected to? I find this connection issue frustrating. Thanks.Re: Could not parse XML inputThank you very much. Austin. It's a Config.js program, embedded in Home page setting / "Page". It's look like this: var APPTOKEN = "dwnt9wipc3cvfcg6nvd****ps4"; var userIDs = new Object(); var tblProject = "bjtm***m9"; var tblProjectFields = new Object(); tblProjectFields['PrimaryKey'] = 3; //CLIST BUILDER tmpFields = new Array(); for (el in tblProjectFields) tmpFields.push(tblProjectFields[el]) var tblProjectCLIST = tmpFields.join("."); delete tmpFields; Re: Could not parse XML inputThank you. I am trying to copy a record. I don't know how to answer webhooks questions. I am using a add-on program developed by others. The program works well till this error only happens to one specific record. Could not parse XML input Hi there, When I was trying to copy a project this morning. A strange error happened. There is an error message that flashes so quickly I can't read it. In the end, it leads me to a page saying "Project Not Found". But the project itself can be edit normally. Finally, I got the message via slow motion video. Here is the message. "Could not parse XML input. XML Parsing Error. not well-formed (invalid token) at line 1 column 307 (which is byte 307). " The weird thing is that it only happens to one specific project. Is there anyone see this problem or error message before? Thank you very much. NingRE: August 27th 2PM EST-Ask Me Anything-Cloudpipes, Automation, and Integration with Jay JamisonWhat will be the process to get new connections/channels/services added?Re: Is there a way to prevent a user from being able to click on linked fields in a report or form?EOTI App?Re: Is there a way to prevent a user from being able to click on linked fields in a report or form?There is only one app now but I can build a 2nd one with just the fields I need.This application will just be for the client portal pulling in the fields I need and refreshing hourly and the client will have access to this app, not the main one. So it will be a QB to QB connected table. I've done it before for a different company years ago and it worked well. Just takes a bit to set up.Re: Is there a way to prevent a user from being able to click on linked fields in a report or form?I think I've solved my own issue - I've done this a long time ago: create a cross-application relationship and just have those fields and look-up fields from my main app and not linkable. Do you think this is an option?