SC Error Log Blank Title 83867

Yahoo Archive
1
Charlie (and others), I was able to get this to work pretty easily.

Basically I put a condition after the update to check for error number > 0. If it finds one, I have a poster after that that dumps the file into an output folder.

Works like a charm, thanks for the direction,
Ken

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Charlie Wilson
Sent: Tuesday, October 13, 2009 9:51 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SC Error Log



There are a lot of different ways to do this. I think I may have a sample
somewhere I will post it to the group later.

Rob Bucek(SP?) may have already done that. Check the online files section.

~Charlie

_____

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of
Ken Williams
Sent: Tuesday, October 13, 2009 10:34 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] SC Error Log

I've only ran it in our test environment.

I'm still new to SC, I'll look into the kick out file for each fail. Any
quick tips?

Thanks,
Ken

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of Charlie Wilson
Sent: Tuesday, October 13, 2009 8:35 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: RE: [Vantage] SC Error Log

You could have made it kick out a file for each failed part but since you
have already run it I don't know of anything except the admin console.

~Charlie

_____

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com>
.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups
<mailto:vantage%40yahoogroups.com> .com<mailto:vantage%40yahoogroups.com>]
On Behalf Of
Ken Williams
Sent: Tuesday, October 13, 2009 10:11 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com>
.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] SC Error Log

We've done a mass update to our parts database by exporting to Excel,
modifying and re-importing via SC.

This has worked well, the problem I have is we've literally updated 8000
parts...and to find the ones that had issue using the admin console isn't
very easily done.

Is there a filter or a way, perhaps through SQL, to get only the part
imports that had errors?

Ken

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
2
We've done a mass update to our parts database by exporting to Excel, modifying and re-importing via SC.

This has worked well, the problem I have is we've literally updated 8000 parts...and to find the ones that had issue using the admin console isn't very easily done.

Is there a filter or a way, perhaps through SQL, to get only the part imports that had errors?

Ken


[Non-text portions of this message have been removed]
3
You could have made it kick out a file for each failed part but since you
have already run it I don't know of anything except the admin console.



~Charlie

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Ken Williams
Sent: Tuesday, October 13, 2009 10:11 AM
To: vantage@yahoogroups.com
Subject: [Vantage] SC Error Log





We've done a mass update to our parts database by exporting to Excel,
modifying and re-importing via SC.

This has worked well, the problem I have is we've literally updated 8000
parts...and to find the ones that had issue using the admin console isn't
very easily done.

Is there a filter or a way, perhaps through SQL, to get only the part
imports that had errors?

Ken

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
4
I've only ran it in our test environment.

I'm still new to SC, I'll look into the kick out file for each fail. Any quick tips?

Thanks,
Ken

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Charlie Wilson
Sent: Tuesday, October 13, 2009 8:35 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SC Error Log



You could have made it kick out a file for each failed part but since you
have already run it I don't know of anything except the admin console.

~Charlie

_____

From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of
Ken Williams
Sent: Tuesday, October 13, 2009 10:11 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] SC Error Log

We've done a mass update to our parts database by exporting to Excel,
modifying and re-importing via SC.

This has worked well, the problem I have is we've literally updated 8000
parts...and to find the ones that had issue using the admin console isn't
very easily done.

Is there a filter or a way, perhaps through SQL, to get only the part
imports that had errors?

Ken

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
5
There are a lot of different ways to do this. I think I may have a sample
somewhere I will post it to the group later.



Rob Bucek(SP?) may have already done that. Check the online files section.



~Charlie

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Ken Williams
Sent: Tuesday, October 13, 2009 10:34 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] SC Error Log





I've only ran it in our test environment.

I'm still new to SC, I'll look into the kick out file for each fail. Any
quick tips?

Thanks,
Ken

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
[mailto:vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com] On
Behalf Of Charlie Wilson
Sent: Tuesday, October 13, 2009 8:35 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Subject: RE: [Vantage] SC Error Log

You could have made it kick out a file for each failed part but since you
have already run it I don't know of anything except the admin console.

~Charlie

_____

From: vantage@yahoogroups <mailto:vantage%40yahoogroups.com>
.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups
<mailto:vantage%40yahoogroups.com> .com<mailto:vantage%40yahoogroups.com>]
On Behalf Of
Ken Williams
Sent: Tuesday, October 13, 2009 10:11 AM
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com>
.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] SC Error Log

We've done a mass update to our parts database by exporting to Excel,
modifying and re-importing via SC.

This has worked well, the problem I have is we've literally updated 8000
parts...and to find the ones that had issue using the admin console isn't
very easily done.

Is there a filter or a way, perhaps through SQL, to get only the part
imports that had errors?

Ken

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
6
Ken, do you have a sub-workflow in your process? I know you can filter
the results of a sub-workflow. If not try putting a condition on your
links to only send if there is an error.

Dan

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Ken Williams
Sent: Tuesday, October 13, 2009 7:11 AM
To: vantage@yahoogroups.com
Subject: [Vantage] SC Error Log




We've done a mass update to our parts database by exporting to Excel,
modifying and re-importing via SC.

This has worked well, the problem I have is we've literally updated 8000
parts...and to find the ones that had issue using the admin console
isn't very easily done.

Is there a filter or a way, perhaps through SQL, to get only the part
imports that had errors?

Ken

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]