Hello,
I am importing records from excel. This was working fine from last year.
In our QA environment, I started getting this error.
Note: in Import structure I have changed datatypes of four attributes from text to date. In DEV environment it is working fine but we started getting this error after deploying to QA.
Please advice.
Thanks and Regards,
Suraj Borade
André Vieira wrote: Hello Sir,
I am sorry because I haven't post my question separately. Because I have same question.
"None of the column headers match with the record attributes".
At the time of ExportToExcel I have set Date column as Text DataType and used DateToText() function to convert it into Text format. Because I am showing "-" OR "TBD" text depends on condition into date column.
e.g.
Date 05-16-2013 OR Date "-" OR Date "TBD" i.e. I have set date column to Text datatype
At time of ImportToExcel I have used TextToDate() to assign date value to respective date column.
Please suggest me, How to solve above error.
Thanks and Regards,
Pradeep Chavhan
Ricardo Silva wrote:
I think you guys are confusing some stuff. And before I continue, please note that the rest of this post is my personal opinion on the matter, it is not meant to be an official OutSystems positioning.
I fully agree with Eric when he says that SOAP and (maybe) REST with JSON are essential for the OutSystems Platform to be able to interface with other systems.
As such, having these capabilities built into the platform offers a great advantage for developers attempting to leverage the OutSystems Platform in their landscape (and also for OutSystems to be able to get into those customers).
However, even if XML is the basis of SOAP, this does not necessarily extend to XML. While I recognize it would remove a lot of pain from developing in the situations where it's needed, I do not believe that XML manipulation belongs as a built-in capability of the OutSystems Platform. This includes X-Path, Serialization, XSD, etc.
I think that enterprises should preferably use SOAP and / or REST to expose their services, instead of relying on weakly typed stuff like XML contracts.
As such I am perfectly ok with this being a community driven effort instead of an OutSystems driven effort. True that the current implementation was done by an OutSystems employee (a long long time ago), but the community should be able to produce this component (or another like it).
Both XML Records and ardoJSON heavily rely on how the code was generated, but (at least ardoJSON) there's nothing done here that someone with proper .NET coding skills couldn't come up with. What I did to generate the bindings for ardoJSON was to reverse engineer how the OutSystems Platform is generating structures and use reflection to access and fill up this data.
What I would really like to see is the OutSystems Platform provide mechanisms to make this kind of approach more ... approachable. If there was a proper API to introspect structures within extensions and a way for me to generate a structure in Service Studio, I (or anyone in the community) could make much more out of XML Records and ardoJSON, without a need for OutSystems to intervene.
So, instead of asking OutSystems to provide you with the tools to address your specific concerns, I think that the community should be asking OutSystems to provide the APIs for the community to be able to build upon the Platform and come up with the weird niche solutions for ourselves.
I agree with you for the most part, however generating XML based on XSD schema (encapsulated in a WSDL or not) is not a niche solution.
In fact its what's holding back the Outsystems platform from being incorporated at a bigger rate in large and medium sized enterprise application landscapes.
Looking at the pricing of Outsystems, it aims at these large and medium enterprises as customers, who rely on Outsystems to be a low-code platform, and would be delighted not to have the need to have their developers build custom .net code.
Because large enterprises, without exception, have an application landscape with many applications that need to be integrated, Outsystems should consider it self-interest to have their platform integrate properly
Doug_inVA wrote:
Here's a question...and forgive my ignorance if it doesn't make sense, not a developer. This extension works assuming the platform server has access to the target machine. What if you had a requirement in a closed network where the platform server could not access a local resource. How could you create a socket within the browser to talk directly to an on-net resource. I know it can be done with JS (Chrome Secure Shell) but can it be done using this library? Could it be done with the library in conjunction with JS?
Hi Doug,
This component runs in the server only. You may be able to achieve something similar with a browser plugin, (such as Secure Shell, which I believe is not just plain JS) and in that case you won't need this component.
Hello Justin,
Thans for your reply. I totally agree with you about logging into the application, but as you might know, some companies don't like major changes ;)
Kind Regards
Martin
Like I said before, use advanced queries.
Mind you, the limitation is in the fact you cannot pivot dynamically, you have to know upfront how many columns you end up with.
can you provide a simple oml, so I can check it?
No problem. The intention is quite correct.
There is a difference in speed, but it's not really an issue now.
Thanks for the reply!
Well, like the stacktrace says.
Not every wsdl can be imported by Outsystems. Biggest issue are the dynamic-complextypes. which in a way is understanable that Outsystems is not able to import.
Imho it's a big design-flaw in wsdl and not from Outsystems, but hey, who am I :)
Either import the wsdl via Integration studio or alter the wsdl to make it simpler.
Ah thanks Pedro, that helps a lot! The only attribute that my extended "Client" entity has which the User entity doesn't is "Surname"... Then I will just have a "Client" entity with the "Surname" attribute and link it via a 1-1 relationship with the system's User entity?
I've done that and I have also changed my entity structures quite a bit... but now I'm getting a LOT of database integrity errors. Is there a quick and easy method to force OutSystems to update the DB to match my new entity structure? Or even just to wipe the DB clean and start it again using my new entity structure? How would you suggest I go about handling this?
Hi,
You should be able to publish it directly in 9.1, at least in a .NET environment. Did you try?
Thank you
I doubt it honestly. I'm using a personal cloud environment.
Is there a way to do it?
Hello,
"None of the column headers match with the record attributes". This exception throws when I import the excel.
At the time of ExportToExcel I have set Date column as Text DataType and used DateToText() function to convert it into Text format. Because I am showing "-" OR "TBD" text depends on condition into date column.
e.g.
Date Column
05-16-2013
"-"
"TBD"
i.e. I have set date column to Text datatype
At time of ImportToExcel I have used TextToDate() to assign date value to respective date column.
Please suggest me, How to solve above error.
Thanks and Regards,
Pradeep Chavhan
The ability to clone an extension would be a really really nice-to-have. :-)
There could be some magic feature that would make this time saver feature. :-)
Then we could make a simple query to build the 'skeleton' of a query and then introduce the aditional rules that cannot be defined in a simple query.
When dealing with mathematical calculations or complex queries it's easy to lose track of parentheses.
Check the attached image for an example of highlighted parentheses on Notepad++.
Specially when we are integrating with other systems we need to create an structure to send just 2 attributes of our Entity, and in those cases we need to design an advanced query instead of doing a simple query to retrieve that 2 attributes.
Users, log-in logic should be improved to allow better mechanisms like, detect and lock a user who is trying to brute-forcely log-in, and optionaly show a Captcha.
This has been requested again and again by users