Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Friday, November 22, 2024 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Web Forums - SalesLogix Web Platform & Application Architect
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to SalesLogix Web Platform & Application Architect | New ThreadView:  Search:  
 Author  Thread: SLX Mobile Ticket list - error
ambuenaventura
Posts: 27
 
SLX Mobile Ticket list - errorYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 26 Oct 15 6:21 AM

Need assistance, please


I just configured the SLX mobile and I can browse it in using Mozilla Firefox.


For the built in entities such as Account, Contacts and others, I have no problem getting inside the page. 


But in the Ticket profile, I received an error  "A server error occurred while requesting data"


I am using SLX 7.5.4 and SLX mobile ver 1.1


Any inputs, please


Many thanks


 

[Reply][Quote]
Jose Urena
Posts: 92
 
Re: SLX Mobile Ticket list - errorYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 02 Nov 15 8:23 AM

First, you should upgrade your mobile version to 2.x.  You will thank me later.


The error you are seing is because you have null values on fields the mobile portal uses in the Ticket query.


The portal show in the list, the Ticket number, the subject, the contact (lastname, firstname), the account, and the responsable of the ticket (ASSIGNEDTOID).


Start by running the following query, and start working on that 20 records so you can find what of the fields is giving you the error.


The query the portal runs is:


SELECT TOP 20 this_.TICKETID as TICKETID130_2_, this_.ACCOUNTPRODUCTID as ACCOUNTP2_130_2_, this_.ADDKNOWLEDGE as ADDKNOWL3_130_2_, this_.ALERT as ALERT130_2_, this_.ALTERNATEKEYPREFIX as ALTERNAT5_130_2_, this_.ALTERNATEKEYSUFFIX as ALTERNAT6_130_2_, this_.AREA as AREA130_2_, this_.ASSIGNEDDATE as ASSIGNED8_130_2_, this_.CATEGORY as CATEGORY130_2_, this_.CLOSED as CLOSED130_2_, this_.CLOSEDONFIRST as CLOSEDO11_130_2_, this_.COMPLETEDDATE as COMPLET12_130_2_, this_.CREATEDATE as CREATEDATE130_2_, this_.CREATEUSER as CREATEUSER130_2_, this_.FIRST as FIRST130_2_, this_.INCIDENTUSED as INCIDEN16_130_2_, this_.ISSUE as ISSUE130_2_, this_.MODIFYDATE as MODIFYDATE130_2_, this_.MODIFYUSER as MODIFYUSER130_2_, this_.NEEDEDBYDATE as NEEDEDB20_130_2_, this_.NOTES as NOTES130_2_, this_.PRIORITY as PRIORITY130_2_, this_.PUBLICACCESSCODE as PUBLICA23_130_2_, this_.RECEIVEDDATE as RECEIVE24_130_2_, this_.STATUSCODE as STATUSCODE130_2_, this_.SUBJECT as SUBJECT130_2_, this_.SUBMITSEARCH as SUBMITS27_130_2_, this_.URGENCYCODE as URGENCY28_130_2_, this_.VIACODE as VIACODE130_2_, this_.WEIGHTCODE as WEIGHTCODE130_2_, this_.TicketNumber as TicketN31_130_2_, this_.RECOMENDACION as RECOMEN32_130_2_, this_.RECEIVEDBYID as RECEIVE33_130_2_, this_.SECCODEID as SECCODEID130_2_, this_.COMPLETEDBYID as COMPLET35_130_2_, this_.ASSIGNEDTOID as ASSIGNE36_130_2_, this_.URGENCYID as URGENCYID130_2_, this_.ACCOUNTID as ACCOUNTID130_2_, this_.CONTACTID as CONTACTID130_2_, this_.CONTRACTID as CONTRACTID130_2_, ticketprob2_.TICKETID as TICKETID137_0_, ticketprob2_.CREATEDATE as CREATEDATE137_0_, ticketprob2_.CREATEUSER as CREATEUSER137_0_, ticketprob2_.MODIFYDATE as MODIFYDATE137_0_, ticketprob2_.MODIFYUSER as MODIFYUSER137_0_, ticketprob2_.NOTES as NOTES137_0_, ticketsolu3_.TICKETID as TICKETID140_1_, ticketsolu3_.CREATEDATE as CREATEDATE140_1_, ticketsolu3_.CREATEUSER as CREATEUSER140_1_, ticketsolu3_.MODIFYDATE as MODIFYDATE140_1_, ticketsolu3_.MODIFYUSER as MODIFYUSER140_1_, ticketsolu3_.NOTES as NOTES140_1_ FROM TICKET this_ left outer join TICKETPROBLEM ticketprob2_ on this_.TICKETID=ticketprob2_.TICKETID left outer join TICKETSOLUTION ticketsolu3_ on this_.TICKETID=ticketsolu3_.TICKETID WITH FIRSTROW 1 ORDER BY this_.TicketNumber asc

[Reply][Quote]
ambuenaventura
Posts: 27
 
Re: SLX Mobile Ticket list - errorYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 04 Nov 15 12:18 AM

Hi Jose,


Thank you for your response.


Found no TicketNumber  and RECOMMENDACION fields on the query.


For the version 2.0 is it compatible for AA ver 7.5.4?


 


Thank you appreciate your feedback.


 


Regards,


ambuenaventura

[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 11/22/2024 2:22:37 PM